Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Josh-E-S/pexip-mgmt-mcp --skill pexip-external-policygit clone --depth 1 https://github.com/Josh-E-S/pexip-mgmt-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/josh-e-s/pexip-mgmt-mcp/pexip-external-policy)<a href="https://agentmods.dev/skills/josh-e-s/pexip-mgmt-mcp/pexip-external-policy"><img src="https://agentmods.dev/badge/skills/josh-e-s/pexip-mgmt-mcp/pexip-external-policy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/josh-e-s/pexip-mgmt-mcp/pexip-external-policy"><img src="https://agentmods.dev/badge/skills/josh-e-s/pexip-mgmt-mcp/pexip-external-policy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00153 | $0.01291 |
| Opus 5 | $0.00077 | $0.00646 |
| Sonnet 5 | $0.00031 | $0.00258 |
| Haiku 4.5 | $0.00015 | $0.00129 |
Grade A, and why
pexip-external-policy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pexip external policy server
The External Policy API lets Pexip Infinity outsource per-call decisions to an HTTP service you run. At well-defined hook points (call setup, service lookup, avatar lookup, participant property lookup), Pexip POSTs a request to your endpoint and applies the JSON response — overriding or augmenting the static dial plan.
Use it when the answer to "where should this call go?" depends on data Pexip doesn't have: your CRM, scheduling system, real-time capacity heuristics, custom auth, dynamic VMRs per booking, etc.
Coverage: the MCP server manages external policy servers today through its generic CRUD tools — the
policy_serverandpolicy_profileresources are in the resource registry (resource_crud.py), solist_resource/get_resource/create_resource/update_resource/delete_resourceall work against them (no dedicated*_external_policy_servertools, and noPEXIP_ALLOW_SECURITY_RESOURCESgate). This skill covers configuring those servers and building the receiver side (the HTTP service Pexip calls).
When to use
- "Build a dynamic VMR per calendar invite" (booking system → VMR creation on demand)
- "Authenticate calls against our SSO before allowing join"
- "Route calls to the lowest-loaded location at the moment of dial"
- "Inject custom branding / display names per call"
- Adding
external_policy_serverCRUD tools to the MCP server
When NOT to use
- Static dial plan with regex matching →
pexip-config-api(gateway_routing_rule) /pexip-operations/dial-plan.md - Persistent VMRs configured ahead of time →
pexip-operations/vmr-administration.md - Runtime kick/lock/mute →
pexip-command-api
Hook points (high-level)
The Pexip External Policy API defines several request types. Pexip POSTs JSON to your endpoint with the request type and call context; you return JSON describing the decision.
| Hook | When fired | Typical use |
|---|---|---|
service_lookup |
A call arrives and Pexip needs to find/create the service it joins | Dynamic VMR creation, per-booking conferences |
participant_lookup |
Participant identity needs verification | SSO / external auth integration |
participant_avatar_lookup |
Need an avatar URL for a participant | Pull from your directory |
participant_properties_lookup |
Need custom properties (display name overrides, role, location) | Per-call branding |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 80 lines · 153 tokens per session scan A f243fe125e4d
pexip-external-policy is a skill published in the GitHub repository Josh-E-S/pexip-mgmt-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 153 tokens to every session and 1,291 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
aws-sdk-java-v2-core
Provides AWS SDK for Java 2.x client configuration, credential resolution, HTTP client tuning, timeout, retry, and testing patterns. Use when creating or hardening AWS service clients, wiring Spring Boot beans, debugging auth or region issues, or choosing sync vs async SDK usage.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…