AI agents call describe_table to retrieve information from Xrm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A 'describe' function in API contexts typically queries and returns information about object structures—in this case, table metadata from Dataverse. No side effects or modifications occur. Confidence is reduced from 0.95 to 0.85 due to missing documentation, but the name and server context strongly support a Read classification with low severity.
From the tool's definition Tool name 'describe_table' strongly suggests schema introspection or metadata retrieval. Given the server context (Dataverse Web API access with read/write operations), this tool most likely retrieves table structure/schema information without modifying data.
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 Xrm, 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 Xrm MCP Server, which means it retrieves data without modifying state.
Register the Xrm 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 Xrm. 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 Xrm MCP server (jukkan/xrm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Xrm, 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.
8 Xrm tools catalogued and risk-classified — across an index of 43,000+ MCP servers.