update_consent

THE RISK

Medium Risk

Why update_consent needs a policy

This tool modifies user consent data reversibly. While the description is minimal ('Update a user'), the tool name and context (consent management system) indicate it changes existing consent records rather than deleting them. This constitutes a Write operation.

From the tool's definition Tool name 'update_consent' and description 'Update a user' indicate modification of user data. The tool operates on consent records within an Apache Unomi user profile system.

Documented attack patterns abuse exactly the kind of access update_consent gives an agent:

POLICY

How to control update_consent

PolicyLayer is an MCP gateway — it sits between your AI agents and Inoyu Apache Unomi MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_consent:

policy.json

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

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

Create a free account and register Inoyu Apache Unomi MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Inoyu Apache Unomi MCP Server tools

Write create_scope Create a new Unomi scope Write update_my_profile Update properties of your profile using environment-provided ID Read get_consent Get specific consent information for a profile Read get_my_profile Get your profile using environment-provided IDs Read get_profile Get a specific Unomi profile by ID Read get_tenant_info Get information about the current tenant (V3 only) Read list_consents List all consents for a profile with optional filtering Read search_profiles Search Unomi profiles

All 9 Inoyu Apache Unomi MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_consent

What does the update_consent tool do? +

Update a user. It is categorised as a Write tool in the Inoyu Apache Unomi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_consent? +

Register the Inoyu Apache Unomi MCP Server MCP server in PolicyLayer and add a rule for update_consent: 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 Inoyu Apache Unomi MCP Server. Nothing to install.

What risk level is update_consent? +

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

Can I rate-limit update_consent? +

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

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

update_consent is provided by the Inoyu Apache Unomi MCP Server MCP server (inoyu-dev/inoyu-mcp-unomi-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Inoyu Apache Unomi MCP Server tool call.

Start from Inoyu Apache Unomi MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →