AI agents use stape_container_proxy_files 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.
The tool supports both reading (getting proxy files) and writing (updating/replacing all proxy files). Since updating/replacing is the most severe applicable category here, it classifies as Write. Replacing all proxy files could have meaningful impact on container behavior, hence medium severity.
From the tool's definition managing container proxy files. Supports getting proxy files and updating/replacing all proxy files for a container
Attacks that exploit this kind of access
Comprehensive tool for managing container proxy files. Supports getting proxy files and updating/replacing all proxy files for a container. 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.
Register the Stape MCP server in PolicyLayer and add a rule for stape_container_proxy_files: 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.
stape_container_proxy_files 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_proxy_files 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_proxy_files. 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_proxy_files 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →