AI agents call school_search 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.
Search operations are read-only with no side effects. The lack of description lowers confidence slightly, but the tool name and the pattern of sibling tools (all ending in _detail, _snapshot, _history, or _search) strongly suggest this retrieves school information without modification. No indication of destructive, financial, or code execution capabilities.
From the tool's definition Tool name 'school_search' indicates a search/query operation. No description provided, but naming convention and server context (ATTOM real estate API) suggest retrieval of school data associated with properties or areas.
Attacks that exploit this kind of access
school_search. 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 school_search: 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.
school_search 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 school_search 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 school_search. 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.
school_search 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 →