Get the current workflow status for a locked issue
AI agents call get_workflow_status to retrieve information from MCP GitHub Issue Priority Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of a workflow for an issue without creating, modifying, deleting, or executing any operations. It is a pure read operation that retrieves status information, posing minimal security risk if misused by an AI agent.
From the tool's definition Tool name 'get_workflow_status' and description 'Get the current workflow status for a locked issue' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the current workflow status for a locked issue. It is categorised as a Read tool in the MCP GitHub Issue Priority Server MCP Server, which means it retrieves data without modifying state.
Register the MCP GitHub Issue Priority Server MCP server in PolicyLayer and add a rule for get_workflow_status: 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 GitHub Issue Priority Server. Nothing to install.
get_workflow_status 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_workflow_status 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_workflow_status. 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_workflow_status is provided by the MCP GitHub Issue Priority Server MCP server (steiner385/mcp-git-issue-priority). 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 →