Check whether the Fidelity browser session is active and logged in.
AI agents call fidelity_status to retrieve information from Claude Fidelity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a passive status check to verify authentication state. It retrieves information about the current session (active/logged-in status) with no side effects, no data modification, no code execution, and no financial operations. This is a classic Read operation. Severity is low because misuse would only leak information about whether a session exists, not credentials or account data itself.
From the tool's definition Tool name 'fidelity_status' and description 'Check whether the Fidelity browser session is active and logged in' indicate a query operation that retrieves session state information without modifying or executing actions.
Attacks that exploit this kind of access
Check whether the Fidelity browser session is active and logged in. It is categorised as a Read tool in the Claude Fidelity MCP Server, which means it retrieves data without modifying state.
Register the Claude Fidelity MCP server in PolicyLayer and add a rule for fidelity_status: 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 Claude Fidelity. Nothing to install.
fidelity_status 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 fidelity_status 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 fidelity_status. 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.
fidelity_status is provided by the Claude Fidelity MCP server (tylerflar/claude-fidelity-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 →