server_status
AI agents call server_status to retrieve information from Pendle Finance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name alone, 'server_status' appears to query the current operational status of the Pendle Finance MCP server, which would be a Read operation (no data modification, no execution of external logic, no financial transactions). The empty description prevents full certainty, slightly reducing confidence, but the naming pattern is consistent with standard health-check or status-query utilities.
From the tool's definition Tool name 'server_status' with empty description suggests a status/health check operation. By naming convention, status tools are read-only queries that return operational state without side effects.
Attacks that exploit this kind of access
server_status. It is categorised as a Read tool in the Pendle Finance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pendle Finance MCP Server MCP server in PolicyLayer and add a rule for 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 Pendle Finance MCP Server. Nothing to install.
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 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 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.
server_status is provided by the Pendle Finance MCP Server MCP server (maneesha029/pendle_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 →