Lists all user tables in the current Firebird database.
AI agents call list-tables 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 performs a read-only query operation that retrieves table names and schema information from the database. It has no side effects, does not execute arbitrary code, does not modify data, and does not delete or create objects. The blast radius of misuse is minimal—an agent could only discover what tables exist in the database.
From the tool's definition Tool name 'list-tables' and description 'Lists all user tables in the current Firebird database' indicate retrieval of schema metadata without any modification or deletion of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Lists all user tables in the current Firebird database. 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 list-tables: 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.
list-tables 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 list-tables 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 list-tables. 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.
list-tables 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 →