get_workitems_ids_assigned_to_user
AI agents call get_workitems_ids_assigned_to_user to retrieve information from WorkItems DevOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries data (work item IDs) with no side effects. It performs a read-only lookup based on user assignment. No creation, modification, deletion, or execution occurs. Severity is low because the blast radius of accidental misuse is minimal—it only exposes existing assignment metadata that the queried user likely already has access to.
From the tool's definition Tool name 'get_workitems_ids_assigned_to_user' uses imperative 'get' pattern, which retrieves work item IDs assigned to a user.
Attacks that exploit this kind of access
get_workitems_ids_assigned_to_user. It is categorised as a Read tool in the WorkItems DevOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WorkItems DevOps MCP Server MCP server in PolicyLayer and add a rule for get_workitems_ids_assigned_to_user: 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 WorkItems DevOps MCP Server. Nothing to install.
get_workitems_ids_assigned_to_user 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_workitems_ids_assigned_to_user 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_workitems_ids_assigned_to_user. 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_workitems_ids_assigned_to_user is provided by the WorkItems DevOps MCP Server MCP server (juanpq26/workitems_devops_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 →