get_field_descriptions
AI agents call get_field_descriptions to retrieve information from Odigo Elastic S2l without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves informational metadata about field schemas and descriptions from Elasticsearch. It has no side effects, does not execute queries against data, and does not modify or delete anything. It is a pure read operation on cluster metadata. The low severity reflects minimal risk from misuse—an AI agent retrieving field metadata poses little danger compared to search or execute operations.
From the tool's definition Tool name 'get_field_descriptions' indicates retrieval of metadata about Elasticsearch fields. The server context describes translating 'technical field names into business knowledge', suggesting this tool queries field definitions/documentation without…
Attacks that exploit this kind of access
get_field_descriptions. It is categorised as a Read tool in the Odigo Elastic S2l MCP Server, which means it retrieves data without modifying state.
Register the Odigo Elastic S2l MCP server in PolicyLayer and add a rule for get_field_descriptions: 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 Odigo Elastic S2l. Nothing to install.
get_field_descriptions 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_descriptions 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_descriptions. 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_descriptions is provided by the Odigo Elastic S2l MCP server (rbeg1/odigo-elastic-s2l-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 →