AI agents call get_project_dashboard to retrieve information from CoordMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or displays project status information for monitoring and visibility purposes. Given the server's focus on coordination and tracking (project state, active agents, tasks), 'get_project_dashboard' almost certainly queries existing data rather than modifying it. The absence of a description lowers confidence slightly, but the naming and server context strongly suggest Read category.
From the tool's definition Tool name 'get_project_dashboard' indicates retrieval of dashboard information. No description provided, but based on naming convention and context as a coordination server for tracking shared state, this is a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
get_project_dashboard. It is categorised as a Read tool in the CoordMCP MCP Server, which means it retrieves data without modifying state.
Register the Coord MCP server in PolicyLayer and add a rule for get_project_dashboard: 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 CoordMCP. Nothing to install.
get_project_dashboard 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_dashboard 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_dashboard. 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_dashboard is provided by the Coord MCP server (siddiquesahabaj/coordmcp). 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 →