get_field_info
AI agents call get_field_info 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.
Based on naming convention and server context (flight data analytics, querying), this tool appears to retrieve metadata about available fields, similar to sibling tools like 'find_fields' and 'list_*' variants. No parameters specified and no description means it likely returns schema/metadata without side effects.
From the tool's definition Tool name 'get_field_info' suggests retrieval of field metadata or schema information. The EMS server description indicates it provides query and analytics capabilities.
Attacks that exploit this kind of access
get_field_info. 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_field_info: 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_field_info 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_field_info 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_field_info. 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_field_info 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 →