Low Risk

get-field-descriptions

Gets the stored descriptions for fields of a specific table (if they exist).

How to control get-field-descriptions ↓

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.

Low Risk

This tool only retrieves metadata (field descriptions) from a Firebird database table. It queries existing data without side effects, modification, or code execution. It cannot delete, create, modify, or execute anything. The blast radius of misuse is minimal - an AI agent could only learn structural information about tables, which poses negligible security risk.

From the tool's definition Tool description states it 'Gets the stored descriptions for fields of a specific table' - a retrieval operation with no modification or execution capability. The verb 'Gets' indicates a simple read operation.

Documented attack patterns abuse exactly the kind of access get-field-descriptions gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Firebird, and nothing reaches the server without passing your rules. This is the rule we recommend for get-field-descriptions:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-field-descriptions": {}
  }
}

get-field-descriptions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Firebird — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get-field-descriptions tool do? +

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.

How do I enforce a policy on get-field-descriptions? +

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.

What risk level is get-field-descriptions? +

get-field-descriptions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-field-descriptions? +

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.

How do I block get-field-descriptions completely? +

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.

What MCP server provides get-field-descriptions? +

get-field-descriptions is provided by the MCP Firebird MCP server (purodelphi/mcpfirebird). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Firebird tool call.

Deterministic rules across all 22 MCP Firebird tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

22 MCP Firebird tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.