AI agents use konsulto_attach_evidence to create or update resources in Konsulto — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Konsulto environment.
The tool creates or adds attachments to an audit system, which is a reversible modification of data. It does not execute external code, delete data irreversibly, or move money. While uploads can affect system state, this is categorized as Write rather than Execute because the tool's primary function is to persist files/content rather than trigger arbitrary code execution.
From the tool's definition "Upload a file (or inline content) as an attachment in the active audit." — explicitly performs file upload and content attachment operations that modify the audit state.
Attacks that exploit this kind of access
Upload a file (or inline content) as an attachment in the active audit. It is categorised as a Write tool in the Konsulto MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Konsulto MCP server in PolicyLayer and add a rule for konsulto_attach_evidence: 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 Konsulto. Nothing to install.
konsulto_attach_evidence 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 konsulto_attach_evidence 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 konsulto_attach_evidence. 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.
konsulto_attach_evidence is provided by the Konsulto MCP server (konsulto/konsulto-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 →