get_hitl_request
[SUPPORT] Read-only: Poll a HITL request for the human's answer. Returns the row including status ('pending'|'answered'|'dismissed') and answer text.
This record as markdown: /tools/io-github-ajc3xc-meridian/get-hitl-request.md
What get_hitl_request does on Meridian
AI agents call get_hitl_request to retrieve information from Meridian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
request_id | string | Yes |
Parameters from the server's own tool schema.
Why get_hitl_request is rated Low
This tool queries and retrieves the status and response of a human-in-the-loop request without modifying any data. It is a read-only polling operation that has no side effects, aligning with the Read category definition of 'retrieves or queries data; no side effects'.
From the tool's definition Tool description explicitly states 'Read-only: Poll a HITL request for the human's answer.' Returns data with no modification capability.
Attacks that exploit this kind of access
The rule that runs get_hitl_request 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 get_hitl_request, this is the rule to start with:
get_hitl_request is read-only, so it stays allowed. 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 get_hitl_request call is checked against it from then on.
Questions about get_hitl_request
[SUPPORT] Read-only: Poll a HITL request for the human's answer. Returns the row including status ('pending'|'answered'|'dismissed') and answer text. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_hitl_request accepts 1 parameter: request_id. Required: 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 get_hitl_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 Meridian. Nothing to install.
get_hitl_request is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_hitl_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 get_hitl_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.
get_hitl_request 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