This record as markdown: /tools/arome3-tempo-mcp/create-policy.md
What create_policy does on Tempo
AI agents use create_policy 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.
Why create_policy is rated Medium
This tool creates new compliance policies that will govern payment behavior and restrictions on the Tempo blockchain system. While policy creation is reversible (policies can be updated or removed), it modifies critical system configuration that affects transaction processing, user access, and compliance controls.
From the tool's definition Tool name 'create_policy' and description 'Create a new TIP-403 compliance policy' indicate data creation and modification of policy configuration on a blockchain stablecoin payment system.
Attacks that exploit this kind of access
The rule that runs create_policy 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 create_policy, this is the rule to start with:
create_policy 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Tempo, apply this rule, and every create_policy call is checked against it from then on.
Questions about create_policy
Create a new TIP-403 compliance policy. 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 create_policy: 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.
create_policy 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 create_policy 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 create_policy. 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.
create_policy 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.
This server
Across the catalogue