Get overall status including discovered servers and SERPAPI_KEY presence
AI agents call get_status to retrieve information from MCP Travel Planner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about discovered servers and API key configuration. It performs no writes, deletions, code execution, or financial operations. The blast radius of misuse is minimal—an agent could only learn system configuration details, which while potentially informative for an attacker, does not directly enable harm. Classified as Read with low severity.
From the tool's definition Tool name 'get_status' and description 'Get overall status including discovered servers and SERPAPI_KEY presence' indicate a retrieval operation that queries system state without modifying data.
Attacks that exploit this kind of access
Get overall status including discovered servers and SERPAPI_KEY presence. It is categorised as a Read tool in the MCP Travel Planner MCP Server, which means it retrieves data without modifying state.
Register the MCP Travel Planner MCP server in PolicyLayer and add a rule for get_status: 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 Travel Planner. Nothing to install.
get_status 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 get_status 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 get_status. 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.
get_status is provided by the MCP Travel Planner MCP server (leonavevor/mcp_travelassistant). 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 →