AI agents call transportation_noise to retrieve information from Attom without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming convention and server context, this appears to retrieve transportation noise data for properties—a Read operation that queries environmental data without side effects. The empty description reduces confidence, but the sibling tool patterns and ATTOM's documented API scope (property details, valuations, assessments) support this classification.
From the tool's definition Tool name 'transportation_noise' with no description provided. Context indicates this server exposes ATTOM real estate API for property details and data retrieval.
Attacks that exploit this kind of access
transportation_noise. It is categorised as a Read tool in the Attom MCP Server, which means it retrieves data without modifying state.
Register the Attom MCP server in PolicyLayer and add a rule for transportation_noise: 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 Attom. Nothing to install.
transportation_noise 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 transportation_noise 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 transportation_noise. 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.
transportation_noise is provided by the Attom MCP server (nkbud/mcp-server-attom). 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 →