get_public_status
Returns the server's public readiness status, version string and discovery URLs. Use this before authenticating to verify the server is reachable and to obtain entry-point URLs. No authentication required. Returns status ('ready'), server name, version, statusUrl and instructionsUrl.
This record as markdown: /tools/de-agentview-agentview-mcp/get-public-status.md
What get_public_status does on agentView
AI agents call get_public_status to retrieve information from agentView without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_public_status is rated Low
This tool only reads and returns public metadata about server status and configuration. It has no side effects, does not execute code or commands, does not modify any data, and does not involve financial transactions. It is a purely informational endpoint used for discovery and connectivity verification.
From the tool's definition Tool description states it 'Returns the server's public readiness status, version string and discovery URLs' with no indication of modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs get_public_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and agentView, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_public_status, this is the rule to start with:
get_public_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect agentView, apply this rule, and every get_public_status call is checked against it from then on.
Questions about get_public_status
Returns the server's public readiness status, version string and discovery URLs. Use this before authenticating to verify the server is reachable and to obtain entry-point URLs. No authentication required. Returns status ('ready'), server name, version, statusUrl and instructionsUrl. It is categorised as a Read tool in the agentView MCP Server, which means it retrieves data without modifying state.
Register the agentView MCP server in PolicyLayer and add a rule for get_public_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 agentView. Nothing to install.
get_public_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_public_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_public_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_public_status is provided by the agentView MCP server (https://agentview.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on agentView, and thousands of servers like it.
This server
Across the catalogue