Create a new data connection in Polytomic.
AI agents use create_connection to create or update resources in Polytomic MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Polytomic MCP Server environment.
The tool creates a new data connection, which is a reversible Write operation that adds a configuration to the system. While it has potential blast radius (creating unauthorized connections could enable data exfiltration or malicious syncs), it is not Destructive (reversible via deletion), not Financial (no direct monetary movement), and not Execute (does not run arbitrary code directly).
From the tool's definition Tool name 'create_connection' and description 'Create a new data connection in Polytomic' indicate creation of a new configuration object that modifies the system state.
Attacks that exploit this kind of access
Create a new data connection in Polytomic. It is categorised as a Write tool in the Polytomic MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Polytomic MCP Server MCP server in PolicyLayer and add a rule for create_connection: 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 Polytomic MCP Server. Nothing to install.
create_connection 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 create_connection 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 create_connection. 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.
create_connection is provided by the Polytomic MCP Server MCP server (therevenueengineer/polytomic-mcp). 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 →