projects_get
Get details about specific GitHub Projects resources. Use this tool to get details about individual projects, project fields, and project items by their unique IDs.
This record as markdown: /tools/github/projects-get.md
What projects_get does on GitHub
AI agents call projects_get to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
owner | string | — | The owner (user or organization login). The name is not case sensitive. |
fields | array | — | Specific list of field IDs to include in the response when getting a project item (e.g. ["102589", "985201", "169875"]). If not provided, only the title field i |
method | string | — | The method to execute |
item_id | number | — | The item's ID. Required for 'get_project_item' method. |
field_id | number | — | The field's ID. Required for 'get_project_field' method. |
owner_type | string | — | Owner type (user or org). If not provided, will be automatically detected. |
project_number | number | — | The project's number. |
status_update_id | string | — | The node ID of the project status update. Required for 'get_project_status_update' method. |
Parameters from the server's own tool schema.
Why projects_get is rated Low
This tool retrieves information about GitHub Projects without creating, modifying, deleting, or executing any operations. It is a read-only query operation that has no side effects on the system or data.
From the tool's definition Tool description states 'Get details about specific GitHub Projects resources' and 'get details about individual projects, project fields, and project items'. The verb 'Get' and the phrase 'details about' indicate a retrieval operation with no modification.
Attacks that exploit this kind of access
The rule that runs projects_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For projects_get, this is the rule to start with:
projects_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every projects_get call is checked against it from then on.
Questions about projects_get
Get details about specific GitHub Projects resources. Use this tool to get details about individual projects, project fields, and project items by their unique IDs. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
projects_get accepts 8 parameters: owner, fields, method, item_id, field_id, owner_type, project_number, status_update_id. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for projects_get: 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. Nothing to install.
projects_get 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 projects_get 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 projects_get. 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.
projects_get is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue