AI agents use crud_create to create or update resources in OODA Computer Control — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OODA Computer Control environment.
This tool creates new data records reversibly. While the broader server has destructive and execute capabilities, this specific tool's function is limited to creating records without deletion or irreversible side effects. Severity is medium because unchecked record creation could cause data bloat or system resource exhaustion, but the operation is reversible via deletion.
From the tool's definition Tool name 'crud_create' and description 'Create a new record in a collection' indicate data creation. The server context emphasizes 'computer control' and operations like file creation, which aligns with Write-category operations.
Documented attack patterns abuse exactly the kind of access crud_create 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_create:
{
"version": "1",
"default": "deny",
"tools": {
"crud_create": {
"limits": [
{
"counter": "crud_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}crud_create 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.
Free to start. No card required.
Create a new record in a collection. It is categorised as a Write tool in the OODA Computer Control MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OODA Computer Control MCP server in PolicyLayer and add a rule for crud_create: 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_create 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 crud_create 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_create. 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_create 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.