Record the host
AI agents use record_drift_outcome to create or update resources in Documcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Documcp environment.
The tool name suggests recording/writing some outcome related to drift (likely configuration or deployment drift in the context of this documentation deployment server). 'Record' implies a Write operation. However, the description is severely truncated and provides almost no useful information, so confidence is low.
From the tool's definition Tool name: 'record_drift_outcome'; description is truncated/uninformative: 'Record the host'
Documented attack patterns abuse exactly the kind of access record_drift_outcome gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Documcp, and nothing reaches the server without passing your rules. This is the rule we recommend for record_drift_outcome:
{
"version": "1",
"default": "deny",
"tools": {
"record_drift_outcome": {
"limits": [
{
"counter": "record_drift_outcome_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}record_drift_outcome 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.
Record the host. It is categorised as a Write tool in the Documcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docu MCP server in PolicyLayer and add a rule for record_drift_outcome: 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 Documcp. Nothing to install.
record_drift_outcome 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 record_drift_outcome 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 record_drift_outcome. 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.
record_drift_outcome is provided by the Docu MCP server (tosin2013/documcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Documcp, 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.
52 Documcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.