AI agents call get_database_tables to retrieve information from Text-to-SQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about database table structure/metadata. It has no side effects, does not execute code, does not modify data, and does not delete anything. It is purely informational (Read category).
From the tool's definition Tool name 'get_database_tables' and description '获取数据库中所有表的列表' (get list of all tables in database) indicate this retrieves metadata about database schema without modifying data.
Documented attack patterns abuse exactly the kind of access get_database_tables gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Text-to-SQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_database_tables:
{
"version": "1",
"default": "deny",
"tools": {
"get_database_tables": {}
}
} get_database_tables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
获取数据库中所有表的列表. It is categorised as a Read tool in the Text-to-SQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Text-to-SQL MCP Server MCP server in PolicyLayer and add a rule for get_database_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 Text-to-SQL MCP Server. Nothing to install.
get_database_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 get_database_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 get_database_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.
get_database_tables is provided by the Text-to-SQL MCP Server MCP server (tmstack/text-to-sql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Text-to-SQL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Text-to-SQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.