List all views in a GitHub Project V2
AI agents call list_project_views 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.
This tool retrieves and enumerates existing views within a GitHub Project without creating, modifying, deleting, or executing any operations. It is a read-only query operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'list_project_views' and description 'List all views in a GitHub Project V2' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all views in a GitHub Project V2. It is categorised as a Read tool in the GitHub Projects MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Projects MCP Server MCP server in PolicyLayer and add a rule for list_project_views: 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.
list_project_views 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 list_project_views 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 list_project_views. 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.
list_project_views is provided by the GitHub Projects MCP Server MCP server (lexmata/github-projects-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 →