stape_container_resources · Stape MCP: Risk & Policy

WHAT IT DOES

What stape_container_resources does on Stape

AI agents use stape_container_resources to create or update resources in Stape — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stape environment.

WHY IT NEEDS A POLICY

Why stape_container_resources needs a policy

The tool supports 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 applies. 'Managing container reactivation' implies triggering state changes on containers, which is a Write-level action.

From the tool's definition managing container reactivation and integration clicks

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stape_container_resources Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stape_container_resources": {
      "limits": [
        {
          "counter": "stape_container_resources_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Stape, so you can run agents against it safely.

FAQ

Questions about stape_container_resources

What does the stape_container_resources tool do? +

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, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on stape_container_resources? +

Register the Stape 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. Nothing to install.

What risk level is stape_container_resources? +

stape_container_resources is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit stape_container_resources? +

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.

How do I block stape_container_resources completely? +

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.

What MCP server provides stape_container_resources? +

stape_container_resources is provided by the Stape MCP server (stape-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.