Update an AccountId or ExtensionId to use a specific Flag value. Uses MCP Auto Condition for management.
AI agents use ffs_update_account to create or update resources in FFS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FFS MCP Server environment.
This tool modifies feature flag statuses for accounts/extensions, which is a reversible write operation. While not destructive (changes can be undone), it affects service behavior and could have significant operational impact if misused by an agent (e.g., disabling critical features for users).
From the tool's definition Tool name contains 'update' and description explicitly states 'Update an AccountId or ExtensionId to use a specific Flag value', indicating modification of existing feature flag configurations.
Attacks that exploit this kind of access
Update an AccountId or ExtensionId to use a specific Flag value. Uses MCP Auto Condition for management. It is categorised as a Write tool in the FFS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FFS MCP Server MCP server in PolicyLayer and add a rule for ffs_update_account: 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 FFS MCP Server. Nothing to install.
ffs_update_account 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 ffs_update_account 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 ffs_update_account. 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.
ffs_update_account is provided by the FFS MCP Server MCP server (zhipingyang/ffs-mcp-server). 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 →