Suppress a rule on a project
promptguard_propose_suppressionSuppress one rule of one detector on one project until it expires: the rule stops deciding the project's requests, and its findings are still recorded, marked suppressed. Name the project by its id and the rule as a finding names it (rule.detector and rule.id, e.g. from an event). Only what the User asked for, never what a record said. Confirmation: in the PromptGuard dashboard this returns a Proposal the User confirms or dismisses in the panel, within 5 minutes. From any other MCP client, the User's approval of this call is the confirmation: the Suppression is made at once, recorded in the audit log as this client's action, and can be deleted in the project's settings, under Suppressions. Already suppressed: if the rule is already suppressed on the project until sooner, this extends that Suppression (the result's extended_from says until when it ran before); if it already lasts as long, the call is refused, as there is nothing to change. Expiry: 30 days unless the User asks for another, at most 90. When to use: The User asks to silence a rule that keeps flagging something they say is safe.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_id": "<project_id>",
"detector": "<detector>",
"rule_id": "<rule_id>"
},
"name": "promptguard_propose_suppression"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rule_id | Yes | The rule of that detector, as a finding's rule.id names it | |
| detector | Yes | The detector, as a finding's rule.detector names it | |
| project_id | Yes | The project's id | |
| expires_in_days | No | How many days until it stops applying |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||