Search for national parks based on state, name, activities, or other criteria
AI agents call findParks to retrieve information from Nationalparks without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches and retrieves data about national parks with no side effects. It is a read-only operation that does not create, modify, delete, or execute any external operations. The low severity reflects minimal risk even if misused by an AI agent, as the worst outcome would be returning irrelevant search results.
From the tool's definition Tool name 'findParks' and description 'Search for national parks based on state, name, activities, or other criteria' indicate a query operation that retrieves park information without modifying or executing any actions.
Attacks that exploit this kind of access
Search for national parks based on state, name, activities, or other criteria. It is categorised as a Read tool in the Nationalparks MCP Server, which means it retrieves data without modifying state.
Register the Nationalparks MCP server in PolicyLayer and add a rule for findParks: 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 Nationalparks. Nothing to install.
findParks 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 findParks 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 findParks. 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.
findParks is provided by the Nationalparks MCP server (mcp-server-nationalparks). 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 →