Low Risk

get-project-items

Get items (issues) from a GitHub Project

How to control get-project-items ↓

AI agents call get-project-items 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.

Low Risk

This tool retrieves or queries project data (issues) without side effects. It does not create, modify, delete, or execute operations. It is a straightforward read operation that returns existing data from GitHub Projects.

From the tool's definition Tool description: 'Get items (issues) from a GitHub Project' — the verb 'Get' and the absence of any modification, deletion, or execution language indicate retrieval only. The tool name 'get-project-items' reinforces this as a query/fetch operation.

Documented attack patterns abuse exactly the kind of access get-project-items gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Projects MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-project-items:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-project-items": {}
  }
}

get-project-items is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register GitHub Projects MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get-project-items tool do? +

Get items (issues) from a GitHub Project. It is categorised as a Read tool in the GitHub Projects MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-project-items? +

Register the GitHub Projects MCP Server MCP server in PolicyLayer and add a rule for get-project-items: 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.

What risk level is get-project-items? +

get-project-items is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-project-items? +

Yes. Add a rate_limit block to the get-project-items 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.

How do I block get-project-items completely? +

Set action: deny in the PolicyLayer policy for get-project-items. 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.

What MCP server provides get-project-items? +

get-project-items is provided by the GitHub Projects MCP Server MCP server (taylor-lindores-reeves/mcp-github-projects). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GitHub Projects MCP Server tool call.

Deterministic rules across all 21 GitHub Projects MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

21 GitHub Projects MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.