check_compliance
Check if a token transfer complies with registered compliance rules.
This record as markdown: /tools/network-tenzro-tenzro/check-compliance.md
What check_compliance does on Tenzro Ledger MCP
AI agents call check_compliance to retrieve information from Tenzro Ledger MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_compliance is rated Low
This is a read operation that checks compliance status of a hypothetical transfer against registered rules. It does not execute the transfer itself, does not delete data, does not move funds, and does not trigger external operations—it only queries and returns compliance information. The operation is non-destructive and has no side effects on actual assets or data.
From the tool's definition The tool name 'check_compliance' and description 'Check if a token transfer complies with registered compliance rules' indicate a query/validation operation that retrieves compliance status without modifying state or executing transfers.
Attacks that exploit this kind of access
The rule that runs check_compliance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_compliance, this is the rule to start with:
check_compliance is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every check_compliance call is checked against it from then on.
Questions about check_compliance
Check if a token transfer complies with registered compliance rules. 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 check_compliance: 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.
check_compliance 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 check_compliance 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 check_compliance. 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.
check_compliance 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.
More on Tenzro Ledger, and thousands of servers like it.
This server
Across the catalogue