patchConsentWithId

Updates, via PATCH, the consent with the given Id.

SERVERFusionauth SOURCE@fusionauth/mcp-api

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-fusionauth-mcp-api/patchconsentwithid.md

WHAT IT DOES

What patchConsentWithId does on Fusionauth

AI agents use patchConsentWithId to create or update resources in Fusionauth, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fusionauth environment.

RISK

Why patchConsentWithId is rated Medium

This tool creates or modifies data (consent records) reversibly through a PATCH operation. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not move money (ruling out Financial).

From the tool's definition Updates, via PATCH, the consent with the given Id — PATCH is an HTTP method for modifying existing resources. The tool directly modifies consent records, which are security-sensitive in an identity/authorization context.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs patchConsentWithId safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Fusionauth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For patchConsentWithId, this is the rule to start with:

patchConsentWithId Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "patchConsentWithId": {
      "limits": [
        {
          "counter": "patchconsentwithid_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about patchConsentWithId

What does the patchConsentWithId tool do? +

Updates, via PATCH, the consent with the given Id. It is categorised as a Write tool in the Fusionauth MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on patchConsentWithId? +

Register the Fusionauth MCP server in PolicyLayer and add a rule for patchConsentWithId: 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 Fusionauth. Nothing to install.

What risk level is patchConsentWithId? +

patchConsentWithId is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit patchConsentWithId? +

Yes. Add a rate_limit block to the patchConsentWithId 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 patchConsentWithId completely? +

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

patchConsentWithId is provided by the Fusionauth MCP server (@fusionauth/mcp-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Fusionauth, and thousands of servers like it.

This server

All 314 Fusionauth tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →