AI agents use answer_worker_questions to create or update resources in Unlimited — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unlimited environment.
The tool appears to write or update state (answering questions that workers are waiting on), which can affect downstream job execution and agent behavior. It is not purely a Read operation (no retrieval indicated), nor Destructive (answering questions is reversible), nor Financial/Execute in the strict sense (no direct code execution or money movement from this tool alone, though it may trigger such operations).
From the tool's definition Tool name 'answer_worker_questions' combined with server description mentioning 'clarification rounds' and 'durable background queues' suggests this tool sends answers/responses that modify the state of background jobs or agent interactions.
Attacks that exploit this kind of access
answer_worker_questions. It is categorised as a Write tool in the Unlimited MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unlimited MCP server in PolicyLayer and add a rule for answer_worker_questions: 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 Unlimited. Nothing to install.
answer_worker_questions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the answer_worker_questions 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 answer_worker_questions. 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.
answer_worker_questions is provided by the Unlimited MCP server (triumsebas/unlimited-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 →