get_result_id
AI agents call get_result_id to retrieve information from EMS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and context within a flight analytics monitoring system suggests this retrieves data (likely a result identifier from a prior query) rather than modifying, executing, or deleting anything. However, confidence is moderate (0.6) due to the completely empty description, which limits certainty about the tool's actual behavior and side effects.
From the tool's definition Tool name 'get_result_id' with empty description. Based on naming convention and sibling tools on this EMS server (query_database, query_flight_analytics, list_databases, get_assets, get_field_info), this appears to be a retrieval operation that fetches or…
Attacks that exploit this kind of access
get_result_id. It is categorised as a Read tool in the EMS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EMS MCP Server MCP server in PolicyLayer and add a rule for get_result_id: 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 EMS MCP Server. Nothing to install.
get_result_id 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_result_id 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_result_id. 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_result_id is provided by the EMS MCP Server MCP server (mattsq/ems-mcp). 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 →