Import findings into the current graph from SARIF or weAudit.
AI agents use augment_findings to create or update resources in Trailmark MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trailmark MCP Server environment.
The tool writes findings data into an existing graph structure, which is a reversible modification. It does not execute arbitrary code, delete data, or move money. The blast radius is medium because incorrect or malicious findings could mislead security analysis, but the operation itself is not destructive and can be undone or corrected by clearing annotations or reimporting.
From the tool's definition Tool description states 'Import findings into the current graph' — this creates or modifies data in the graph by adding findings from external sources (SARIF or weAudit formats).
Attacks that exploit this kind of access
Import findings into the current graph from SARIF or weAudit. It is categorised as a Write tool in the Trailmark MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trailmark MCP Server MCP server in PolicyLayer and add a rule for augment_findings: 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 Trailmark MCP Server. Nothing to install.
augment_findings 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 augment_findings 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 augment_findings. 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.
augment_findings is provided by the Trailmark MCP Server MCP server (parsiya/trailmark-mcp-server). 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 →