Creates a new policy in the project
AI agents use create-policy to create or update resources in Openfort MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Openfort MCP Server environment.
This tool creates new policy configurations in a blockchain/wallet infrastructure system. Creation of policies is reversible (policies can be modified or deleted later), placing it in the Write category rather than Destructive. However, severity is high because misconfigured policies could affect account security, transaction rules, or access controls across the project.
From the tool's definition Tool name 'create-policy' and description 'Creates a new policy in the project' indicate data creation. Sibling tools include 'create-account', 'create-user', 'create-project', and 'delete-contract', confirming this server manages consequential resources…
Attacks that exploit this kind of access
Creates a new policy in the project. It is categorised as a Write tool in the Openfort MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Openfort MCP Server 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 Openfort MCP Server. 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 Openfort MCP Server MCP server (openfort-xyz/-deprecated-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →