AI agents use content to create or update resources in Proxima — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proxima environment.
An AI agent can call content faster than any human can review — one bad instruction and it creates or modifies resources in Proxima by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
General text/content tool: summarize, write, brainstorm, howto, analyze, extract, or improve. For code use the code tools; for research with sources use deep_search. It is categorised as a Write tool in the Proxima MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Proxima MCP server in PolicyLayer and add a rule for content: 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 Proxima. Nothing to install.
content 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 content 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 content. 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.
content is provided by the Proxima MCP server (zen4-bit/proxima). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
content is one line of Proxima's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →