Add or update documentation. Stores a new document or updates an existing one.
AI agents use add-doc to create or update resources in CHECK-MODULE MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CHECK-MODULE MCP Server environment.
This tool creates new documents or modifies existing ones in the documentation system. These are Write operations—they change state but are reversible (documents can be updated again or removed). The severity is medium because misuse could corrupt internal documentation, affecting users relying on accurate docs, but the damage is containable through subsequent corrections or version control.
From the tool's definition Tool description states 'Add or update documentation. Stores a new document or updates an existing one.' The verbs 'add' and 'update' combined with 'stores' indicate reversible creation and modification of data.
Documented attack patterns abuse exactly the kind of access add-doc gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CHECK-MODULE MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add-doc:
{
"version": "1",
"default": "deny",
"tools": {
"add-doc": {
"limits": [
{
"counter": "add-doc_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add-doc 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.
Add or update documentation. Stores a new document or updates an existing one. It is categorised as a Write tool in the CHECK-MODULE MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CHECK-MODULE MCP Server MCP server in PolicyLayer and add a rule for add-doc: 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 CHECK-MODULE MCP Server. Nothing to install.
add-doc 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 add-doc 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 add-doc. 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.
add-doc is provided by the CHECK-MODULE MCP Server MCP server (muhammedehab35/check-module-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CHECK-MODULE MCP Server, 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.
6 CHECK-MODULE MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.