Check if a TIP-20 transfer is allowed by the token
AI agents call check_transfer_compliance to retrieve information from Tempo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access check_transfer_compliance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tempo, and nothing reaches the server without passing your rules. This is the rule we recommend for check_transfer_compliance:
{
"version": "1",
"default": "deny",
"tools": {
"check_transfer_compliance": {}
}
}check_transfer_compliance is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.
check_transfer_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_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.
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.
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.
Start from Tempo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
61 Tempo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.