[OCD] 変更をコミット (git:
AI agents use ocd_commit to create or update resources in OCD - Organized Context Datastore (MCP) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OCD - Organized Context Datastore (MCP) environment.
This tool commits (persists) changes to the OCD datastore's files. While not destructive in itself, committing modifies the stored state irreversibly in the sense that it records a permanent version history entry. This is a Write operation because it creates/modifies persistent data structures.
From the tool's definition Tool name 'ocd_commit' combined with description mentioning 'git' and '変更をコミット' (Japanese: 'commit changes') indicates the tool persists modifications to a structured datastore.
Attacks that exploit this kind of access
[OCD] 変更をコミット (git:. It is categorised as a Write tool in the OCD - Organized Context Datastore (MCP) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OCD - Organized Context Datastore (MCP) MCP server in PolicyLayer and add a rule for ocd_commit: 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 OCD - Organized Context Datastore (MCP). Nothing to install.
ocd_commit 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 ocd_commit 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 ocd_commit. 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.
ocd_commit is provided by the OCD - Organized Context Datastore (MCP) MCP server (teamstove/organized-context-datastore-mcp). 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 →