project_status
AI agents call project_status to retrieve information from MidOS - MCP Community Library without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, classification relies on the tool name and server context. 'project_status' most naturally reads as a status query that retrieves information about a project's current state, with no indication of modification, deletion, or execution of external code. This is consistent with the Read category.
From the tool's definition Tool name 'project_status' suggests retrieval of project state/metadata. Description is empty, limiting direct evidence, but naming conventions on this read-oriented server (episodic_search, get_eureka, get_protocol, get_skill, get_truth) indicate…
Attacks that exploit this kind of access
project_status. It is categorised as a Read tool in the MidOS - MCP Community Library MCP Server, which means it retrieves data without modifying state.
Register the MidOS - MCP Community Library MCP server in PolicyLayer and add a rule for 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 MidOS - MCP Community Library. Nothing to install.
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 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 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.
project_status is provided by the MidOS - MCP Community Library MCP server (midos-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 →