log_consent_event

A write tool on the Metis Public Health MCP server.

SERVERMetis Public Health SOURCEsveritg/metis_ph

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/sveritg-metis-ph/log-consent-event.md

WHAT IT DOES

What log_consent_event does on Metis Public Health

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

RISK

Why log_consent_event is rated Medium

The name 'log_consent_event' strongly implies writing a consent-related record (e.g., a patient or research participant consent event) to a log or database. In a public health context, consent records are sensitive and legally significant. The empty description lowers confidence, but logging/writing a consent event is most likely a Write operation.

From the tool's definition Tool name: log_consent_event — description is empty/uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs log_consent_event safely

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

log_consent_event Rate-limited

log_consent_event 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": {
    "log_consent_event": {
      "limits": [
        {
          "counter": "log_consent_event_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 Metis Public Health, apply this rule, and every log_consent_event call is checked against it from then on.

FAQ

Questions about log_consent_event

What does the log_consent_event tool do? +

log_consent_event is a write tool on the Metis Public Health MCP server. It is categorised as a Write tool in the Metis Public Health MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log_consent_event? +

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

What risk level is log_consent_event? +

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

Can I rate-limit log_consent_event? +

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

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

log_consent_event is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Metis Public Health, and thousands of servers like it.

This server

All 277 Metis Public Health tools →

Across the catalogue

calendar_create_event on Apple Apps MCP → The MCP Attack Database →

Guides

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