This record as markdown: /tools/hybridlabor-api-aos/elicit-missing-args.md
What elicit_missing_args does on Aos
AI agents invoke elicit_missing_args to trigger actions in Aos. 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 elicit_missing_args is rated High
The tool uses an LLM to propose values for a tool call, which constitutes triggering an external operation (LLM inference) and potentially auto-filling arguments for subsequent tool calls. This is more than a read — it executes an AI inference step and could feed into downstream tools. The description is somewhat vague, lowering confidence.
From the tool's definition 'Use the schema + LLM to propose values for a tool call' — this tool invokes an LLM to generate and propose argument values, triggering an external AI operation whose effects depend on the arguments it produces
Attacks that exploit this kind of access
The rule that runs elicit_missing_args safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For elicit_missing_args, this is the rule to start with:
elicit_missing_args 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 Aos, apply this rule, and every elicit_missing_args call is checked against it from then on.
Questions about elicit_missing_args
Use the schema + LLM to propose values for a tool call. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aos MCP server in PolicyLayer and add a rule for elicit_missing_args: 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 Aos. Nothing to install.
elicit_missing_args 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 elicit_missing_args 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 elicit_missing_args. 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.
elicit_missing_args is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue