get_project_v2
AI agents call get_project_v2 to retrieve information from GitHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix indicates a retrieval operation with no side effects. Despite the empty description reducing confidence slightly, the tool name and context within a GitHub API server (which provides project metadata queries) point to a Read operation. This would retrieve GitHub Projects v2 information without modifying state.
From the tool's definition Tool name 'get_project_v2' follows a GET/read pattern typical of query operations. Description is empty, but the naming convention strongly suggests data retrieval.
Attacks that exploit this kind of access
get_project_v2. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for get_project_v2: 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 MCP Server. Nothing to install.
get_project_v2 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_v2 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_v2. 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_v2 is provided by the GitHub MCP Server MCP server (software-engineer-mj/github-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 →