Remove an address from a TIP-403 policy blacklist (unblock the address).
AI agents use remove_from_blacklist to create or update resources in Tempo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tempo environment.
This tool modifies a compliance/security policy by removing an address from a blacklist, effectively unblocking it from transactions. This is a reversible write operation (the address can be re-added), but carries high severity because misuse by an AI agent could unblock malicious or sanctioned addresses, enabling prohibited financial activity on the Tempo stablecoin network.
From the tool's definition Remove an address from a TIP-403 policy blacklist (unblock the address)
Documented attack patterns abuse exactly the kind of access remove_from_blacklist 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 remove_from_blacklist:
{
"version": "1",
"default": "deny",
"tools": {
"remove_from_blacklist": {
"limits": [
{
"counter": "remove_from_blacklist_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} remove_from_blacklist stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Remove an address from a TIP-403 policy blacklist (unblock the address). It is categorised as a Write tool in the Tempo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tempo MCP server in PolicyLayer and add a rule for remove_from_blacklist: 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.
remove_from_blacklist 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 remove_from_blacklist 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 remove_from_blacklist. 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.
remove_from_blacklist 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.