Update an existing policy
AI agents use update-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.
The tool modifies policy configurations within Openfort's wallet infrastructure. This is a Write operation (reversible change to data/config) rather than Destructive (no deletion or overwrite of entire policies). Severity is medium because policy misconfigurations could affect wallet security or transaction behavior, but the operation is reversible and doesn't directly move funds or execute external code.
From the tool's definition Tool name 'update-policy' with description 'Update an existing policy' indicates modification of existing configuration data. Sibling tools include create operations (create-policy, create-project) confirming this server manages mutable resources.
Attacks that exploit this kind of access
Update an existing policy. 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 update-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.
update-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 update-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 update-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.
update-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 →