Check the current status of an AccountId or ExtensionId in a Flag.
AI agents call ffs_check_account to retrieve information from FFS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a non-destructive query/retrieval of feature flag status for a given account or extension. The verb 'check' and the action of reading status information classify it as a Read operation. While feature flag information could be sensitive, the capability itself only reads existing state without side effects.
From the tool's definition Tool name 'ffs_check_account' and description 'Check the current status of an AccountId or ExtensionId in a Flag' indicate a query operation that retrieves flag status information without modifying any data.
Attacks that exploit this kind of access
Check the current status of an AccountId or ExtensionId in a Flag. It is categorised as a Read tool in the FFS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FFS MCP Server MCP server in PolicyLayer and add a rule for ffs_check_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_check_account 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 ffs_check_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_check_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_check_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 →