Retrieves detailed information about a specific Dataverse table including its metadata, properties, and configuration. Use this to inspect table definitions and understand table structure.
AI agents call get_dataverse_table to retrieve information from Dataverse MCP Server 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 operation on Dataverse metadata. It retrieves and inspects table information without creating, modifying, deleting, or executing operations. The blast radius if misused is minimal—an agent could gain knowledge of table structure but cannot alter data or trigger side effects. This is a straightforward Read operation.
From the tool's definition Tool name and description: 'Retrieves detailed information' and 'inspect table definitions' indicate querying/inspection without modification. The verb 'Retrieves' and context of understanding structure confirm data retrieval only.
Documented attack patterns abuse exactly the kind of access get_dataverse_table gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dataverse MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dataverse_table:
{
"version": "1",
"default": "deny",
"tools": {
"get_dataverse_table": {}
}
} get_dataverse_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.
Retrieves detailed information about a specific Dataverse table including its metadata, properties, and configuration. Use this to inspect table definitions and understand table structure. It is categorised as a Read tool in the Dataverse MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for get_dataverse_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 Dataverse MCP Server. Nothing to install.
get_dataverse_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 get_dataverse_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 get_dataverse_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.
get_dataverse_table is provided by the Dataverse MCP Server MCP server (mwhesse/dataverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dataverse 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.
71 Dataverse MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.