list_hitl_requests

SERVERMeridian SOURCE@meridianmcp/mcp

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/list-hitl-requests.md

WHAT IT DOES

What list_hitl_requests does on Meridian

AI agents call list_hitl_requests 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
`limit`	integer	—	Max results, default 50.
`status`	string	—	Filter: omit for pending+recent-answered (default), 'pending', 'answered', 'dismissed', or 'all'.
`project_id`	string	—	Optional. Omit to list across all projects.
`project_name`	string	—	Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given.

Parameters from the server's own tool schema.

RISK

Why list_hitl_requests is rated Low

This tool retrieves and queries HITL (human-in-the-loop) request data with optional filtering by project_id and status. It performs no mutations, executions, or side effects—purely informational retrieval. The read-only designation and list operation confirm the Read category. Severity is low because listing queued requests poses minimal risk even if misused by an AI agent.

From the tool's definition Tool explicitly marked '[SUPPORT] Read-only: List HITL requests' and returns pending queue and historical data from the last 24 hours. No create, modify, delete, or execute operations described.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_hitl_requests 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 list_hitl_requests, this is the rule to start with:

list_hitl_requests Allowed

list_hitl_requests is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_hitl_requests": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every list_hitl_requests call is checked against it from then on.

FAQ

Questions about list_hitl_requests

What does the list_hitl_requests tool do? +

[SUPPORT] Read-only: List HITL requests without needing UUIDs. OMIT project_id to list pending HITLs across ALL your projects (matches the dashboard) — planning sessions should call it this way so HITLs filed under another project aren't missed (a common cause of false 'no pending HITLs' confidence). Pass project_id to scope to one project. Returns pending queue plus answered/dismissed from the last 24 h by default so planning sessions can see what was recently decided without a separate call. Pass status='pending' for only the active queue, or status='answered'/'dismissed'/'all' for specific history. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does list_hitl_requests accept? +

list_hitl_requests accepts 4 parameters: limit, status, project_id, project_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_hitl_requests? +

Register the Meridian MCP server in PolicyLayer and add a rule for list_hitl_requests: 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.

What risk level is list_hitl_requests? +

list_hitl_requests is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_hitl_requests? +

Yes. Add a rate_limit block to the list_hitl_requests 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.

How do I block list_hitl_requests completely? +

Set action: deny in the PolicyLayer policy for list_hitl_requests. 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.

What MCP server provides list_hitl_requests? +

list_hitl_requests 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.

KEEP EXPLORING

More on Meridian, and thousands of servers like it.

This server

All 175 Meridian tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →