Get high-level project summary (task counts, dates, critical path length, source format)
AI agents call get_project_summary to retrieve information from Project Management AI Analysis without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns project metadata without modifying, deleting, executing code, or triggering external operations. The data retrieved is informational and read-only. Low severity as misuse would only expose project information, not cause data loss or harmful actions.
From the tool's definition Tool retrieves high-level project data: 'task counts, dates, critical path length, source format'. Keywords 'get' and 'summary' indicate read-only retrieval with no side effects.
Attacks that exploit this kind of access
Get high-level project summary (task counts, dates, critical path length, source format). It is categorised as a Read tool in the Project Management AI Analysis MCP Server, which means it retrieves data without modifying state.
Register the Project Management AI Analysis MCP server in PolicyLayer and add a rule for get_project_summary: 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 Project Management AI Analysis. Nothing to install.
get_project_summary 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_summary 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_summary. 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_summary is provided by the Project Management AI Analysis MCP server (pm-mcp-servers). 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 →