Get information about visitor centers and their operating hours
AI agents call getVisitorCenters 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 retrieves public information about visitor centers—a read-only operation that queries existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal; an agent could only retrieve more visitor center information than necessary, which has no security or operational impact.
From the tool's definition Tool name 'getVisitorCenters' and description 'Get information about visitor centers and their operating hours' indicate pure data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get information about visitor centers and their operating hours. 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 getVisitorCenters: 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.
getVisitorCenters 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 getVisitorCenters 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 getVisitorCenters. 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.
getVisitorCenters 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 →