Get server health and service status
AI agents call faber_server_status to retrieve information from Faber MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns server health and service status information. It performs no data modification, deletion, code execution, or financial operations. It is a straightforward informational read operation with minimal blast radius if misused by an AI agent—at worst, it could spam status checks or be used for reconnaissance, but neither causes damage or commits resources.
From the tool's definition Tool name 'faber_server_status' and description 'Get server health and service status' indicate a query operation that retrieves status information without modification or side effects.
Attacks that exploit this kind of access
Get server health and service status. It is categorised as a Read tool in the Faber MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Faber MCP Server MCP server in PolicyLayer and add a rule for faber_server_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 Faber MCP Server. Nothing to install.
faber_server_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 faber_server_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 faber_server_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.
faber_server_status is provided by the Faber MCP Server MCP server (joshtrebilco/faber-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 →