AI agents call describe-table to retrieve information from MCP Server Generator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'describe-table' operation appears to query and retrieve table information (schema, columns, properties) without creating, modifying, or deleting data. This is a typical read operation. The lack of an explicit description prevents higher confidence, but contextual clues from the sibling tools (analyzeData, analyzeServerDependencies) suggest a data inspection utility rather than a destructive or execute operation.
From the tool's definition Tool name 'describe-table' suggests retrieval of table metadata or structure without modification. The empty description reduces confidence, but the naming convention is consistent with read operations like 'describe' commands (e.g., SQL DESCRIBE, database…
Documented attack patterns abuse exactly the kind of access describe-table gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server Generator, and nothing reaches the server without passing your rules. This is the rule we recommend for describe-table:
{
"version": "1",
"default": "deny",
"tools": {
"describe-table": {}
}
}describe-table 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.
describe-table. It is categorised as a Read tool in the MCP Server Generator MCP Server, which means it retrieves data without modifying state.
Register the MCP Server Generator MCP server in PolicyLayer and add a rule for describe-table: 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 Server Generator. Nothing to install.
describe-table 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 describe-table 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 describe-table. 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.
describe-table is provided by the MCP Server Generator MCP server (serhatuzbas/mcp-server-generator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server Generator, 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.
79 MCP Server Generator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.