answer_hitl
[SUPPORT] Answer a pending HITL request programmatically. Marks it answered so the waiting session can resume. Use list_hitl_requests to find request IDs. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata are sent to and stored in Meridian's service; self...
This record as markdown: /tools/io-github-ajc3xc-meridian/answer-hitl.md
What answer_hitl does on Meridian
AI agents use answer_hitl to create or update resources in Meridian, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meridian environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
answer | string | Yes | |
request_id | string | Yes | |
answered_by | string | — | Optional human_id of the answerer. |
Parameters from the server's own tool schema.
Why answer_hitl is rated Medium
This tool writes a response to a pending Human-In-The-Loop request and updates its state to 'answered', allowing a paused session to resume. It creates/modifies persistent state (the HITL request record) and potentially triggers downstream session continuation. It is reversible in the sense that the request record remains (though marked answered), and no data is destroyed.
From the tool's definition Answer a pending HITL request programmatically. Marks it answered so the waiting session can resume.
Attacks that exploit this kind of access
The rule that runs answer_hitl safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For answer_hitl, this is the rule to start with:
answer_hitl stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every answer_hitl call is checked against it from then on.
Questions about answer_hitl
[SUPPORT] Answer a pending HITL request programmatically. Marks it answered so the waiting session can resume. Use list_hitl_requests to find request IDs. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata are sent to and stored in Meridian's service; self-hosted deployments keep them in the configured local SQLite/Postgres database. This data is visible in the dashboard/API and later project context or handoffs. Delete individual tasks, notes, or decisions where supported, or delete the project/account using the documented controls. Do not include secrets. It is categorised as a Write tool in the Meridian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
answer_hitl accepts 3 parameters: answer, request_id, answered_by. Required: answer, request_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian MCP server in PolicyLayer and add a rule for answer_hitl: 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 Meridian. Nothing to install.
answer_hitl 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_hitl 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_hitl. 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_hitl is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue