Check if an address is on the whitelist for a TIP-403 policy.
AI agents call is_whitelisted 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 lookup/query operation to determine whether an address exists on a whitelist. It has no side effects, does not execute transactions, does not modify data, and does not delete or create records. It is purely informational. While the server as a whole handles financial operations (stablecoin payments), this specific tool is a read-only compliance check.
From the tool's definition Tool name 'is_whitelisted' and description 'Check if an address is on the whitelist' indicate a query operation that retrieves whitelist status without modifying any state.
Documented attack patterns abuse exactly the kind of access is_whitelisted 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 is_whitelisted:
{
"version": "1",
"default": "deny",
"tools": {
"is_whitelisted": {}
}
} is_whitelisted 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 an address is on the whitelist for a TIP-403 policy. 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 is_whitelisted: 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.
is_whitelisted 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 is_whitelisted 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 is_whitelisted. 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.
is_whitelisted 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.