Show read-only effective configuration and startup policy status
AI agents call gateway.config_status to retrieve information from PMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays configuration information without side effects. The explicit designation of 'read-only' in the description confirms it performs a query operation (Read category). Severity is low because viewing configuration status poses minimal risk even if misused by an agent — it cannot modify systems or access sensitive runtime data beyond already-deployed configuration state.
From the tool's definition Tool name contains 'status' and description states 'Show read-only effective configuration and startup policy status' — explicitly read-only operation that retrieves configuration state without modification.
Documented attack patterns abuse exactly the kind of access gateway.config_status 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.config_status:
{
"version": "1",
"default": "deny",
"tools": {
"gateway.config_status": {}
}
}gateway.config_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Show read-only effective configuration and startup policy status. It is categorised as a Read tool in the PMCP MCP Server, which means it retrieves data without modifying state.
Register the P MCP server in PolicyLayer and add a rule for gateway.config_status: 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.config_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gateway.config_status 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.config_status. 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.config_status 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.