Get project status including agent and integration health.
AI agents call get_project_status to retrieve information from MCP Server for Coroot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves observability status information about a project (agent health, integration health) without creating, modifying, deleting, or executing any operations. It is a read-only query operation typical of monitoring and observability platforms.
From the tool's definition Tool name 'get_project_status' and description 'Get project status including agent and integration health' indicate retrieval of monitoring data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_project_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Coroot, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_project_status": {}
}
}get_project_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get project status including agent and integration health. It is categorised as a Read tool in the MCP Server for Coroot MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Coroot 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 MCP Server for Coroot. 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 MCP Server for Coroot MCP server (jamesbrink/mcp-coroot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for Coroot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
61 MCP Server for Coroot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.