get_project_status
A read tool on the Metis Public Health MCP server.
This record as markdown: /tools/sveritg-metis-ph/get-project-status.md
What get_project_status does on Metis Public Health
AI agents call get_project_status to retrieve information from Metis Public Health without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_project_status is rated Low
The name 'get_project_status' follows a read-pattern (get + noun) and returns state information. No parameters, modification operations, or side effects are apparent from the name. In the context of a research/knowledge management server like Metis, status retrieval is a non-destructive information query.
From the tool's definition Tool name 'get_project_status' indicates retrieval of status information without modification. The description is empty, so classification is based on semantic analysis of the name alone.
Attacks that exploit this kind of access
The rule that runs get_project_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_project_status, this is the rule to start with:
get_project_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 Metis Public Health, apply this rule, and every get_project_status call is checked against it from then on.
Questions about get_project_status
get_project_status is a read tool on the Metis Public Health MCP server. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for get_project_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 Metis Public Health. Nothing to install.
get_project_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_project_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_project_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_project_status is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metis Public Health, and thousands of servers like it.
This server
Across the catalogue