AI agents use konsulto_add_evidence_to_finding 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.
This tool modifies existing audit findings by attaching evidence to them. While the operation is reversible (evidence can presumably be removed), it changes the state of findings in the cybersecurity audit platform. This is a Write operation rather than Read (it modifies data), Execute (it doesn't run arbitrary code or external operations), or Destructive (the action is reversible).
From the tool's definition The tool description states it can 'Graft an already-uploaded attachment into an existing finding', which modifies an existing finding by adding evidence to it.
Attacks that exploit this kind of access
Graft an already-uploaded attachment into an existing finding\. 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_add_evidence_to_finding: 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_add_evidence_to_finding 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_add_evidence_to_finding 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_add_evidence_to_finding. 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_add_evidence_to_finding 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 →