Test connectivity to the SpiderFoot server.
AI agents call ping to retrieve information from SpiderFoot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A ping operation is a basic diagnostic check that verifies server availability without side effects. It does not retrieve sensitive data, modify state, execute code, delete information, or move money. While it provides some information about server status, this is minimal and non-sensitive metadata. Classified as Read (low severity) since it only queries connectivity status.
From the tool's definition Tool is named 'ping' with description 'Test connectivity to the SpiderFoot server.' This performs a simple connectivity test with no data retrieval, modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Test connectivity to the SpiderFoot server. It is categorised as a Read tool in the SpiderFoot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SpiderFoot 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 SpiderFoot 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 SpiderFoot MCP Server MCP server (marlinkcyber/spiderfoot-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 →