AI agents call get_publishing_webserver_status to retrieve information from SEED MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and reports the status of a webserver (whether it is running and its port number). It has no side effects, does not execute operations, does not modify data, and does not delete or move resources. It is a simple status check query, fitting the Read category with low severity since discovering a port number poses minimal risk even if misused.
From the tool's definition Tool name 'get_publishing_webserver_status' and description 'Check if SEED publishing webserver is running and on what port' indicate a query operation that retrieves server state information without modifying anything.
Attacks that exploit this kind of access
Check if SEED publishing webserver is running and on what port. It is categorised as a Read tool in the SEED MCP MCP Server, which means it retrieves data without modifying state.
Register the SEED MCP server in PolicyLayer and add a rule for get_publishing_webserver_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 SEED MCP. Nothing to install.
get_publishing_webserver_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_publishing_webserver_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_publishing_webserver_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_publishing_webserver_status is provided by the SEED MCP server (sancovp/seed-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 →