request_manual_issue_screening_toggle
[SUPPORT] 5dfe34b2 — request enabling/disabling the OFF-by-default opt-in extension that lets the automated GitHub-issue comment/propose flow (never auto-close) also act on issues Meridian did not itself create, gated behind hardcoded content screening. enable=true ALWAYS files a require_human=tr...
This record as markdown: /tools/io-github-ajc3xc-meridian/request-manual-issue-screening-toggle.md
What request_manual_issue_screening_toggle does on Meridian
AI agents use request_manual_issue_screening_toggle 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 |
|---|---|---|---|
enable | boolean | Yes | true to request enabling (files a human-only HITL); false to disable immediately. |
context | string | — | |
project_id | string | — | Optional — a project to file the enable-request HITL under; defaults to a workspace-level request. |
session_id | string | — | |
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.
Why request_manual_issue_screening_toggle is rated Medium
This is a Write operation because it persistently modifies configuration state (toggling an extension on/off) and creates HITL queue entries. It is reversible—the enable/disable toggle can be switched back. While it involves a HITL queue (coordination aspect), the primary function is to write/modify settings.
From the tool's definition The tool 'request_manual_issue_screening_toggle' modifies persistent state on the Meridian server by enabling or disabling an automated extension.
Attacks that exploit this kind of access
The rule that runs request_manual_issue_screening_toggle 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 request_manual_issue_screening_toggle, this is the rule to start with:
request_manual_issue_screening_toggle 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 request_manual_issue_screening_toggle call is checked against it from then on.
Questions about request_manual_issue_screening_toggle
[SUPPORT] 5dfe34b2 — request enabling/disabling the OFF-by-default opt-in extension that lets the automated GitHub-issue comment/propose flow (never auto-close) also act on issues Meridian did not itself create, gated behind hardcoded content screening. enable=true ALWAYS files a require_human=true HITL (kind/require_human are hardcoded — this tool cannot be used to self-escalate; only a genuine human answering in the dashboard/API can enable it). enable=false disables immediately with no HITL (fail-safe direction) and is audit-logged either way. 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.
request_manual_issue_screening_toggle accepts 5 parameters: enable, context, project_id, session_id, project_name. Required: enable. 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 request_manual_issue_screening_toggle: 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.
request_manual_issue_screening_toggle 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 request_manual_issue_screening_toggle 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 request_manual_issue_screening_toggle. 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.
request_manual_issue_screening_toggle 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