list_repo_pulls
AI agents call list_repo_pulls to retrieve information from Tangled MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix combined with context from sibling tools clearly indicates this retrieves or queries pull requests data without modifying, deleting, or executing any operations. This is a standard Read operation on a git collaboration platform. The empty description prevents higher confidence, but the naming pattern is unambiguous.
From the tool's definition Tool name is 'list_repo_pulls' which indicates listing/querying pull requests. The empty description limits certainty, but 'list_' prefix is a strong signal of a read-only retrieval operation with no side effects, consistent with sibling tools like…
Attacks that exploit this kind of access
list_repo_pulls. It is categorised as a Read tool in the Tangled MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tangled MCP Server MCP server in PolicyLayer and add a rule for list_repo_pulls: 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 Tangled MCP Server. Nothing to install.
list_repo_pulls 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_repo_pulls 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_repo_pulls. 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_repo_pulls is provided by the Tangled MCP Server MCP server (zzstoatzz/tangled-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 →