Get a GitHub Project V2 with all fields and their options
AI agents call ralph_hero__get_project to retrieve information from Ralph Hero without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries project configuration data from GitHub Projects V2. It performs a read-only operation that returns existing project information without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could retrieve project metadata but cannot alter workflows, delete data, or trigger external actions.
From the tool's definition Tool name 'get_project' and description 'Get a GitHub Project V2 with all fields and their options' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get a GitHub Project V2 with all fields and their options. It is categorised as a Read tool in the Ralph Hero MCP Server, which means it retrieves data without modifying state.
Register the Ralph Hero MCP server in PolicyLayer and add a rule for ralph_hero__get_project: 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 Ralph Hero. Nothing to install.
ralph_hero__get_project 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 ralph_hero__get_project 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 ralph_hero__get_project. 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.
ralph_hero__get_project is provided by the Ralph Hero MCP server (ralph-hero-mcp-server). 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 →