Get detailed column information for a specific table including data types, lengths, nullability, defaults, and CCSID. ${sessionConfig ?
AI agents call describe_table to retrieve information from Db2i without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that retrieves schema metadata. It has no side effects, cannot modify data, and presents minimal risk even if misused by an AI agent. The worst outcome would be information disclosure of table structure, which is typically not sensitive compared to actual data or destructive operations.
From the tool's definition Tool description explicitly states 'Get detailed column information' which is a retrieval operation. Server description emphasizes 'read-only SQL commands and schema inspection tools' with 'secure access to table metadata.' The tool returns structural…
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 Db2i, 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.
Get detailed column information for a specific table including data types, lengths, nullability, defaults, and CCSID. ${sessionConfig ?. It is categorised as a Read tool in the Db2i MCP Server, which means it retrieves data without modifying state.
Register the Db2i 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 Db2i. 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 Db2i MCP server (strom-capital/mcp-server-db2i). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Db2i, 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.
7 Db2i tools catalogued and risk-classified — across an index of 43,000+ MCP servers.