get_project_details
AI agents call get_project_details to retrieve information from GitHub Projects MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and server context strongly suggest this retrieves project metadata without modification. It follows the Read category pattern of the server's other tools. Empty description prevents certainty, but the naming convention and sibling tool patterns (all get_* operations) indicate a query/retrieval function with no side effects.
From the tool's definition Tool name 'get_project_details' and server context indicate data retrieval from GitHub Projects. The server description emphasizes 'scraping and retrieving data' with sibling tools (get_project_iterations, get_repo_issues, get_repo_prs) all being read…
Attacks that exploit this kind of access
get_project_details. It is categorised as a Read tool in the GitHub Projects MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Projects MCP Server MCP server in PolicyLayer and add a rule for get_project_details: 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 GitHub Projects MCP Server. Nothing to install.
get_project_details 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_details 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_details. 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_details is provided by the GitHub Projects MCP Server MCP server (jamescalam/github-projects-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 →