変更をコミットします (draft_commitモード用)
AI agents use 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 changes to the OCD datastore, making modifications permanent within the system. While the changes are reversible (via delete or edit operations), the commit action itself irreversibly writes the current state. This is a Write operation (not Destructive, since the underlying data can still be modified or deleted by other tools).
From the tool's definition Tool name 'commit' and description '変更をコミットします' (Japanese: 'Commits changes') indicate this tool persists modifications to the structured datastore.
Attacks that exploit this kind of access
変更をコミットします (draft_commitモード用). 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 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.
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 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 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.
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 →