Returns service status / health
AI agents call get_status to retrieve information from PDF Generator API 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 simple health check or status retrieval operation. It only queries and returns information about the service state without modifying, creating, deleting, or executing any operations. It falls squarely into the Read category as it has no capability to change system state or trigger actions. Severity is low because misuse would only retrieve harmless diagnostic information.
From the tool's definition Tool name is 'get_status' and description states it 'Returns service status / health'. This is a read-only query operation that retrieves status information with no side effects.
Attacks that exploit this kind of access
Returns service status / health. It is categorised as a Read tool in the PDF Generator API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PDF Generator API MCP Server MCP server in PolicyLayer and add a rule for get_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 PDF Generator API MCP Server. Nothing to install.
get_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_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_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_status is provided by the PDF Generator API MCP Server MCP server (pdfgeneratorapi/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 →