Cek status server.
AI agents call server_status to retrieve information from PDP MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple health-check or status monitoring tool that returns information about server availability and operational metrics. It has no capability to modify data, execute arbitrary operations, or cause destructive effects. The blast radius of misuse is minimal—at worst, an attacker gains knowledge of server uptime but cannot leverage this tool to cause harm. This clearly fits the Read category.
From the tool's definition Tool name 'server_status' with description 'Cek status server' (Check server status) performs a query operation that retrieves the current operational state of the server without modifying any data or triggering side effects.
Attacks that exploit this kind of access
Cek status server. It is categorised as a Read tool in the PDP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PDP 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 PDP 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 PDP MCP Server MCP server (vibecoding4-jc/pdp-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 →