Gets the stored descriptions for fields of a specific table (if they exist).
AI agents call get-field-descriptions to retrieve information from MCP Firebird without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves field metadata (descriptions) from a database table schema. It performs no data modification, deletion, or code execution—only reading and returning information about field documentation. The operation is purely informational with no side effects, making it a straightforward Read category tool with low severity.
From the tool's definition Tool name contains 'get' and description states 'Gets the stored descriptions for fields of a specific table'. This is a read-only retrieval operation that queries metadata without modification.
Attacks that exploit this kind of access
Gets the stored descriptions for fields of a specific table (if they exist). It is categorised as a Read tool in the MCP Firebird MCP Server, which means it retrieves data without modifying state.
Register the MCP Firebird 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 MCP Firebird. 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 MCP Firebird MCP server (luancamara/mcpfirebird). 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 →