Get fields in a project (including status/column options)
AI agents call get_project_fields to retrieve information from GitHub Project MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about project fields and their configuration options. It performs no modifications, deletions, or external operations. It is a straightforward data retrieval function, fitting the Read category. The blast radius is minimal since reading project structure poses no risk of data loss or unintended changes.
From the tool's definition Tool name is 'get_project_fields' and description states 'Get fields in a project (including status/column options)' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get fields in a project (including status/column options). It is categorised as a Read tool in the GitHub Project MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Project MCP Server MCP server in PolicyLayer and add a rule for get_project_fields: 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 Project MCP Server. Nothing to install.
get_project_fields 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_fields 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_fields. 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_fields is provided by the GitHub Project MCP Server MCP server (jaqarx/github-project-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 →