AI agents call crud_batch_read to retrieve information from OODA Computer Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the server offering destructive and execute capabilities (shell commands, file operations, deletions), this specific tool is narrowly scoped to reading/retrieving data in parallel. The verb 'read' and absence of any write, execute, or destructive language confirms it performs query-like operations with no side effects. Low severity reflects minimal blast radius from misuse.
From the tool's definition Tool name contains 'read' and description explicitly states 'Read multiple records in parallel' with no modification or deletion semantics.
Documented attack patterns abuse exactly the kind of access crud_batch_read gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for crud_batch_read:
{
"version": "1",
"default": "deny",
"tools": {
"crud_batch_read": {}
}
}crud_batch_read 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.
Read multiple records in parallel. It is categorised as a Read tool in the OODA Computer Control MCP Server, which means it retrieves data without modifying state.
Register the OODA Computer Control MCP server in PolicyLayer and add a rule for crud_batch_read: 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 OODA Computer Control. Nothing to install.
crud_batch_read 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 crud_batch_read 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 crud_batch_read. 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.
crud_batch_read is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OODA Computer Control, 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.
99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.