remove_from_whitelist

Remove an address from a TIP-403 policy whitelist.

SERVERTempo SOURCEarome3/tempo-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arome3-tempo-mcp/remove-from-whitelist.md

WHAT IT DOES

What remove_from_whitelist does on Tempo

AI agents call remove_from_whitelist to permanently remove resources in Tempo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why remove_from_whitelist is rated Critical

Removing an address from a whitelist is an irreversible access-control change that revokes the address's ability to participate in compliant transfers. This cannot be automatically undone and could block legitimate users or contracts from transacting, making it a destructive operation with high blast radius in a financial payment system.

From the tool's definition Remove an address from a TIP-403 policy whitelist

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_from_whitelist safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tempo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_from_whitelist, this is the rule to start with:

remove_from_whitelist Hidden

remove_from_whitelist is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_from_whitelist"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tempo, apply this rule, and every remove_from_whitelist call is checked against it from then on.

FAQ

Questions about remove_from_whitelist

What does the remove_from_whitelist tool do? +

Remove an address from a TIP-403 policy whitelist. It is categorised as a Destructive tool in the Tempo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_from_whitelist? +

Register the Tempo MCP server in PolicyLayer and add a rule for remove_from_whitelist: 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 remove_from_whitelist? +

remove_from_whitelist is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_from_whitelist? +

Yes. Add a rate_limit block to the remove_from_whitelist 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 remove_from_whitelist completely? +

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

remove_from_whitelist 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.

KEEP EXPLORING

More on Tempo, and thousands of servers like it.

This server

All 61 Tempo tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →