Check server liveness and get basic server information
AI agents call ping to retrieve information from LegCo Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The ping tool performs a read-only operation to verify server availability and obtain metadata about the server state. This is a passive query with no side effects, data modifications, code execution, or destructive capability. It falls squarely within the Read category as the least severe classification.
From the tool's definition Tool name 'ping' with description 'Check server liveness and get basic server information' indicates a health-check operation that retrieves status data without modifying or executing operations.
Attacks that exploit this kind of access
Check server liveness and get basic server information. It is categorised as a Read tool in the LegCo Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LegCo Search MCP Server MCP server in PolicyLayer and add a rule for ping: 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 LegCo Search MCP Server. Nothing to install.
ping 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 ping 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 ping. 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.
ping is provided by the LegCo Search MCP Server MCP server (yellowcandle/legco-search-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 →