Get issue detail by using issue ID or issue number.
AI agents call get_issue_detail to retrieve information from Leiga MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a retrieval operation that queries existing issue data and returns information. It has no side effects, creates no data, executes no code, and cannot delete or modify resources. It falls squarely within the Read category. The severity is low because the blast radius of retrieving issue details is limited to information disclosure risk, and only if the issue contains sensitive data.
From the tool's definition Tool name is 'get_issue_detail' and description states 'Get issue detail by using issue ID or issue number' — purely retrieves information with no modification or deletion capability.
Attacks that exploit this kind of access
Get issue detail by using issue ID or issue number. It is categorised as a Read tool in the Leiga MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Leiga MCP Server MCP server in PolicyLayer and add a rule for get_issue_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 Leiga MCP Server. Nothing to install.
get_issue_detail 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_issue_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.
Set action: deny in the PolicyLayer policy for get_issue_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.
get_issue_detail is provided by the Leiga MCP Server MCP server (uvidswqkscr89/leiga_mcp_smithery). 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 →