get_deadlines_by_risk

Retrieve all stored deadlines filtered by risk level. Risk levels: overdue (past deadline), critical (≤2 days), high (3-5 days), medium (6-10 days), low (>10 days).

Server Multi-Agent RAG MCP Server tsarri/rag-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_deadlines_by_risk does on Multi-Agent RAG MCP Server

AI agents call get_deadlines_by_risk to retrieve information from Multi-Agent RAG MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_deadlines_by_risk needs a policy

This tool retrieves and filters deadline data based on risk level parameters. It performs no side effects, creates no data, executes no external operations, and causes no irreversible changes. The operation is purely informational query of existing stored deadlines, which is characteristic of a Read category tool.

From the tool's definition Tool name 'get_deadlines_by_risk' and description 'Retrieve all stored deadlines filtered by risk level' indicate a data retrieval operation with no modification or deletion capability.

Questions about get_deadlines_by_risk

What does the get_deadlines_by_risk tool do? +

Retrieve all stored deadlines filtered by risk level. Risk levels: overdue (past deadline), critical (≤2 days), high (3-5 days), medium (6-10 days), low (>10 days). It is categorised as a Read tool in the Multi-Agent RAG MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_deadlines_by_risk? +

Register the Multi-Agent RAG MCP Server MCP server in PolicyLayer and add a rule for get_deadlines_by_risk: 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 Multi-Agent RAG MCP Server. Nothing to install.

What risk level is get_deadlines_by_risk? +

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

Can I rate-limit get_deadlines_by_risk? +

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

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

get_deadlines_by_risk is provided by the Multi-Agent RAG MCP Server MCP server (tsarri/rag-mcp-server). 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.