Get information about fields in an index.
AI agents call get_field_info to retrieve information from NRTSearch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves schema or metadata information about fields in a search index. It has no side effects, cannot modify data, and is a read-only query operation. The blast radius of misuse is minimal—an attacker learning field names poses low risk compared to data exfiltration or destructive actions.
From the tool's definition Tool name 'get_field_info' and description 'Get information about fields in an index' indicate a query operation that retrieves metadata about index structure without modifying data.
Attacks that exploit this kind of access
Get information about fields in an index. It is categorised as a Read tool in the NRTSearch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NRTSearch 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 NRTSearch 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 NRTSearch MCP Server MCP server (tvergilio/nrtsearch-mcp-server). 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 →