get_pull_detail

Get a pull request detail

Server Mcp Gitee @gitee/mcp-gitee
Category Read
Risk class Low
Parameters 33 required

What get_pull_detail does on Mcp Gitee

AI agents call get_pull_detail to retrieve information from Mcp Gitee without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
repo string Yes The path of the repository
owner string Yes The space address to which the repository belongs (the address path of the enterprise, organization or individual)
number number Yes The number of the pull request, must be an integer, not a float

Parameters from the server's own tool schema.

Why get_pull_detail needs a policy

This tool retrieves or queries existing pull request data from Gitee. It performs no create, modify, delete, or execute operations. The action is read-only and has no side effects, making it a Read category tool with low severity.

From the tool's definition Tool name 'get_pull_detail' and description 'Get a pull request detail' indicate a retrieval operation that queries pull request information without modification or side effects.

Questions about get_pull_detail

What does the get_pull_detail tool do? +

Get a pull request detail. It is categorised as a Read tool in the Mcp Gitee MCP Server, which means it retrieves data without modifying state.

What parameters does get_pull_detail accept? +

get_pull_detail accepts 3 parameters: repo, owner, number. Required: repo, owner, number. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_pull_detail? +

Register the Mcp Gitee MCP server in PolicyLayer and add a rule for get_pull_detail: 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 Mcp Gitee. Nothing to install.

What risk level is get_pull_detail? +

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

Can I rate-limit get_pull_detail? +

Yes. Add a rate_limit block to the get_pull_detail 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_pull_detail completely? +

Set action: deny in the PolicyLayer policy for get_pull_detail. 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_pull_detail? +

get_pull_detail is provided by the Mcp Gitee MCP server (@gitee/mcp-gitee). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.