get_workitems_ids_assigned_to_user_by_planned_date

get_workitems_ids_assigned_to_user_by_planned_date

Server WorkItems DevOps MCP Server juanpq26/workitems_devops_mcp
Category Read
Risk class Low
Parameters 00 required

What get_workitems_ids_assigned_to_user_by_planned_date does on WorkItems DevOps MCP Server

AI agents call get_workitems_ids_assigned_to_user_by_planned_date 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.

Why get_workitems_ids_assigned_to_user_by_planned_date needs a policy

This tool retrieves or queries data (work item IDs) based on filter criteria (assigned user and planned date). It has no side effects—it does not create, modify, delete, or execute operations. It falls clearly into the Read category as a query/filter operation.

From the tool's definition Tool name 'get_workitems_ids_assigned_to_user_by_planned_date' indicates retrieval/querying of work item IDs filtered by user assignment and planned date. The server description confirms it supports 'queries, filtering' as core capabilities.

Questions about get_workitems_ids_assigned_to_user_by_planned_date

What does the get_workitems_ids_assigned_to_user_by_planned_date tool do? +

get_workitems_ids_assigned_to_user_by_planned_date. It is categorised as a Read tool in the WorkItems DevOps MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workitems_ids_assigned_to_user_by_planned_date? +

Register the WorkItems DevOps MCP Server MCP server in PolicyLayer and add a rule for get_workitems_ids_assigned_to_user_by_planned_date: 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.

What risk level is get_workitems_ids_assigned_to_user_by_planned_date? +

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

Can I rate-limit get_workitems_ids_assigned_to_user_by_planned_date? +

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

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

get_workitems_ids_assigned_to_user_by_planned_date 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.

// 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.