get_issue_details
AI agents call get_issue_details to retrieve information from RunWhen Platform MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool follows the 'get_*' pattern typical of read operations that retrieve or query existing data without side effects. While the empty description reduces confidence slightly, the semantic meaning of 'get_issue_details' clearly aligns with the Read category. Severity is low because retrieving issue metadata poses minimal risk compared to write, execute, or destructive operations.
From the tool's definition Tool name 'get_issue_details' indicates a retrieval operation that queries issue data. No description provided, but the naming pattern and context within a workspace management platform suggest data retrieval rather than modification or execution.
Attacks that exploit this kind of access
get_issue_details. It is categorised as a Read tool in the RunWhen Platform MCP MCP Server, which means it retrieves data without modifying state.
Register the RunWhen Platform MCP server in PolicyLayer and add a rule for get_issue_details: 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 RunWhen Platform MCP. Nothing to install.
get_issue_details 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_details 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_details. 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_details is provided by the RunWhen Platform MCP server (runwhen-contrib/runwhen-platform-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 →