Tool for retrieving gateway-related resources and configurations. Use the
AI agents call stape_gateway_resource to retrieve information from Stape MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries gateway configurations without inducing side effects. The verb 'retrieving' and lack of any write/execute/delete language clearly places this in the Read category. Severity is low because accessing configuration data poses minimal risk compared to destructive or financial operations, though some gateway configs might be sensitive depending on their nature.
From the tool's definition Tool name 'stape_gateway_resource' and description indicate retrieval of 'gateway-related resources and configurations' with no mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access stape_gateway_resource gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Stape MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stape_gateway_resource:
{
"version": "1",
"default": "deny",
"tools": {
"stape_gateway_resource": {}
}
} stape_gateway_resource 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.
Tool for retrieving gateway-related resources and configurations. Use the. It is categorised as a Read tool in the Stape MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stape MCP Server MCP server in PolicyLayer and add a rule for stape_gateway_resource: 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 Stape MCP Server. Nothing to install.
stape_gateway_resource 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 stape_gateway_resource 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 stape_gateway_resource. 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.
stape_gateway_resource is provided by the Stape MCP Server MCP server (stape-io/stape-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Stape MCP Server, 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.
18 Stape MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.