canton_connected_synchronizers
AI agents call canton_connected_synchronizers to retrieve information from Tenzro Ledger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name pattern 'canton_connected_synchronizers' appears to be a Read operation—likely retrieving information about connected synchronizers in a Canton system. The empty description and naming convention suggest a query/list operation with no side effects. Confidence is moderate (0.6) because the description is uninformative and the tool's actual function cannot be fully verified without documentation.
From the tool's definition Tool name 'canton_connected_synchronizers' suggests querying or retrieving synchronizer connection status; no modifiers like 'update', 'create', 'delete', or 'execute' in the name.
Attacks that exploit this kind of access
canton_connected_synchronizers. It is categorised as a Read tool in the Tenzro Ledger MCP MCP Server, which means it retrieves data without modifying state.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for canton_connected_synchronizers: 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 Tenzro Ledger MCP. Nothing to install.
canton_connected_synchronizers 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 canton_connected_synchronizers 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 canton_connected_synchronizers. 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.
canton_connected_synchronizers is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/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 →