Store credentials for a server and make them available to provisioning.
AI agents use gateway.auth_connect to create or update resources in PMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PMCP environment.
This tool writes security-sensitive data (credentials) to persistent storage for later use. While not destructive (credentials can be replaced), it modifies the authentication state of the gateway and represents a Write operation with high severity due to the sensitive nature of stored credentials and potential for privilege escalation or lateral movement if misused by an AI agent.
From the tool's definition Tool name 'gateway.auth_connect' and description 'Store credentials for a server and make them available to provisioning' indicates the tool creates or modifies credential records in storage.
Documented attack patterns abuse exactly the kind of access gateway.auth_connect gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for gateway.auth_connect:
{
"version": "1",
"default": "deny",
"tools": {
"gateway.auth_connect": {
"limits": [
{
"counter": "gateway.auth_connect_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}gateway.auth_connect stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Store credentials for a server and make them available to provisioning. It is categorised as a Write tool in the PMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the P MCP server in PolicyLayer and add a rule for gateway.auth_connect: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches PMCP. Nothing to install.
gateway.auth_connect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gateway.auth_connect rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for gateway.auth_connect. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
gateway.auth_connect is provided by the P MCP server (viperjuice/pmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 PMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.