Check API key status — returns login, margin mode (hedging/netting), permissions, and tier. Call this once at session start.
AI agents call get_auth_status to retrieve information from XBTFX MCP Trading Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves authentication and account configuration metadata. It performs a read-only query to display the current state of API credentials and account settings. There is no data creation, modification, deletion, code execution, or financial transaction involved.
From the tool's definition The tool description explicitly states it 'returns' information about API key status, login state, margin mode, permissions, and tier. The verb 'check' and 'returns' indicate a query operation with no side effects.
Attacks that exploit this kind of access
Check API key status — returns login, margin mode (hedging/netting), permissions, and tier. Call this once at session start. It is categorised as a Read tool in the XBTFX MCP Trading Server MCP Server, which means it retrieves data without modifying state.
Register the XBTFX MCP Trading Server MCP server in PolicyLayer and add a rule for get_auth_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 XBTFX MCP Trading Server. Nothing to install.
get_auth_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 get_auth_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 get_auth_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.
get_auth_status is provided by the XBTFX MCP Trading Server MCP server (xbtfx/xbtfx-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 →