AI agents call extract_data to retrieve information from Proxima without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'extract_data' indicates a read operation that retrieves or queries data without modification. However, confidence is reduced to 0.65 because the description is empty, leaving ambiguity about what data is extracted, from where, and whether the operation has any side effects.
From the tool's definition Tool name 'extract_data' suggests data retrieval/query operation. No description provided to confirm scope or side effects.
Documented attack patterns abuse exactly the kind of access extract_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proxima, and nothing reaches the server without passing your rules. This is the rule we recommend for extract_data:
{
"version": "1",
"default": "deny",
"tools": {
"extract_data": {}
}
}extract_data 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.
extract_data. It is categorised as a Read tool in the Proxima MCP Server, which means it retrieves data without modifying state.
Register the Proxima MCP server in PolicyLayer and add a rule for extract_data: 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.
extract_data 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 extract_data 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 extract_data. 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.
extract_data 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.
Deterministic rules across all 50 Proxima tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
50 Proxima tools catalogued and risk-classified — across an index of 42,500+ MCP servers.