merge_datasets
AI agents use merge_datasets to create or update resources in MCP Tabular Data Analysis Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Tabular Data Analysis Server environment.
The tool name 'merge_datasets' suggests creating new data structures by combining existing datasets, which is a modification operation. Without a detailed description, we cannot determine if the merge is reversible or destructive. In the context of a data analysis server with sibling tools like 'export_data' and 'create_pivot_table', this likely creates derived data structures.
From the tool's definition Tool name 'merge_datasets' indicates a data operation that combines or modifies datasets. No description provided to clarify scope or reversibility.
Attacks that exploit this kind of access
merge_datasets. It is categorised as a Write tool in the MCP Tabular Data Analysis Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Tabular Data Analysis Server MCP server in PolicyLayer and add a rule for merge_datasets: 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 Tabular Data Analysis Server. Nothing to install.
merge_datasets is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the merge_datasets 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 merge_datasets. 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.
merge_datasets is provided by the MCP Tabular Data Analysis Server MCP server (k02d/mcp-tabular). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →