Comprehensive tool for managing container resources. Supports getting code settings scripts, example domain records, last subscription promo code, and managing container reactivation and integration clicks. Use the
AI agents use stape_container_resources to create or update resources in Stape MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stape MCP Server environment.
The tool description mentions both read operations (getting code settings scripts, example domain records, last subscription promo code) and write/action operations (managing container reactivation and integration clicks). Per the rules, the most severe applicable category wins. 'Container reactivation' and 'integration clicks' imply triggering state changes or actions, which elevates this to Write.
From the tool's definition managing container reactivation and integration clicks
Documented attack patterns abuse exactly the kind of access stape_container_resources 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_container_resources:
{
"version": "1",
"default": "deny",
"tools": {
"stape_container_resources": {
"limits": [
{
"counter": "stape_container_resources_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} stape_container_resources 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.
Comprehensive tool for managing container resources. Supports getting code settings scripts, example domain records, last subscription promo code, and managing container reactivation and integration clicks. Use the. It is categorised as a Write tool in the Stape MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Stape MCP Server MCP server in PolicyLayer and add a rule for stape_container_resources: 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_container_resources 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 stape_container_resources 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_container_resources. 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_container_resources 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.