AI agents call pinned_scan_diff to retrieve information from Pinnedai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes code diff data to identify security risks. It performs inspection and querying of git state—characteristic of Read category. However, the severity is high because the tool operates in a security-critical context (bug prevention, credential leak detection) where an agent could misuse the scanning logic to identify high-risk patterns for malicious purposes, or could suppress warnings.
From the tool's definition Tool scans git diff for risky surfaces (routes, webhooks, middleware, env changes) but description cuts off mid-sentence. Name and function indicate analysis/inspection of code changes without modification.
Attacks that exploit this kind of access
Scan the current git diff (vs origin/main by default) for risky surfaces — new routes, webhook handlers, middleware changes, env file edits — that don. It is categorised as a Read tool in the Pinnedai MCP Server, which means it retrieves data without modifying state.
Register the Pinnedai MCP server in PolicyLayer and add a rule for pinned_scan_diff: 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 Pinnedai. Nothing to install.
pinned_scan_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pinned_scan_diff 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 pinned_scan_diff. 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.
pinned_scan_diff is provided by the Pinnedai MCP server (pinnedai/pinnedai). 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 →