handle_request
Main AIDE router. Takes a natural language request and decides whether to schedule a meeting, assign a task, or run admin checks. Returns a structured RouterOutput.
This record as markdown: /tools/nitrostack/handle-request.md
What handle_request does on Nitrostack
AI agents invoke handle_request to trigger actions in Nitrostack. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why handle_request is rated High
Routes natural language to multiple actions including scheduling, task assignment, and admin operations.
From the tool's definition decides whether to schedule a meeting, assign a task, or run admin checks
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs handle_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For handle_request, this is the rule to start with:
handle_request stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every handle_request call is checked against it from then on.
Questions about handle_request
Main AIDE router. Takes a natural language request and decides whether to schedule a meeting, assign a task, or run admin checks. Returns a structured RouterOutput. It is categorised as a Execute tool in the Nitrostack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nitrostack MCP server in PolicyLayer and add a rule for handle_request: 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 Nitrostack. Nothing to install.
handle_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the handle_request 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 handle_request. 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.
handle_request is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
Across the catalogue