AI agents call vehicle.investigations to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves publicly available vehicle investigation data from NHTSA without creating, modifying, deleting, or executing any operations. It has no side effects or financial implications. The only limitation noted is lack of filtering support, which further confirms it is a simple read operation. No AI misuse scenario would result in data loss, code execution, or financial harm.
From the tool's definition Tool description states it retrieves 'NHTSA open vehicle investigations' as a 'Chronological feed' with no modification, deletion, or execution capability mentioned.
Attacks that exploit this kind of access
NHTSA open vehicle investigations, newest first. Chronological feed — filters (make/model/year) are not supported by upstream. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for vehicle.investigations: 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 Mcp. Nothing to install.
vehicle.investigations 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 vehicle.investigations 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 vehicle.investigations. 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.
vehicle.investigations is provided by the MCP server (@2sio/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 →