New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

check_transfer_compliance

Check if a TIP-20 transfer is allowed by the token

SERVERTempo SOURCEarome3/tempo-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arome3-tempo-mcp/check-transfer-compliance.md

What check_transfer_compliance does on Tempo

AI agents call check_transfer_compliance to retrieve information from Tempo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_transfer_compliance is rated Low

This tool performs a compliance check—a data retrieval and validation operation with no side effects. It queries the token's transfer rules to determine if a transfer would be permitted, similar to a permissions lookup. While deployed on a financial blockchain payment server, the tool itself does not execute transfers, modify balances, or commit financial obligations; it merely reports on compliance status.

From the tool's definition Tool name 'check_transfer_compliance' and description 'Check if a TIP-20 transfer is allowed' indicate a read-only query operation that validates transfer eligibility without executing or modifying any state.

Questions about check_transfer_compliance

What does the check_transfer_compliance tool do? +

Check if a TIP-20 transfer is allowed by the token. It is categorised as a Read tool in the Tempo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_transfer_compliance? +

Register the Tempo MCP server in PolicyLayer and add a rule for check_transfer_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 Tempo. Nothing to install.

What risk level is check_transfer_compliance? +

check_transfer_compliance is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_transfer_compliance? +

Yes. Add a rate_limit block to the check_transfer_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.

How do I block check_transfer_compliance completely? +

Set action: deny in the PolicyLayer policy for check_transfer_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.

What MCP server provides check_transfer_compliance? +

check_transfer_compliance is provided by the Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Tempo, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tempo's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.