lgpd_data_subject_rights_automator

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io

High RISK CLASS

Category Execute

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/lgpd-data-subject-rights-automator.md

WHAT IT DOES

What lgpd_data_subject_rights_automator does on Mcp Knowledge

AI agents invoke lgpd_data_subject_rights_automator to trigger actions in Mcp Knowledge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`async`	boolean	—	If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
`scope`	array	—	Optional list of data categories to limit the request
`urgency`	string	—	Priority level for processing
`requestType`	string	Yes	Type of LGPD request
`userIdentifier`	string	Yes	CPF, email, or other unique identifier for the data subject

Parameters from the server's own tool schema.

RISK

Why lgpd_data_subject_rights_automator is rated High

This tool executes compliance workflows that include data erasure and rectification operations, which are irreversible or semi-reversible data modifications. The most severe action it can take is deletion (erasure), which would be Destructive, but since it also handles access and rectification in an automated workflow context and the description emphasizes process automation rather than direct deletion, Execute is…

From the tool's definition Automates LGPD Data Subject Access Requests (DSARs)... handling Brazil-specific data retention, erasure, and access workflows... request type (access/rectification/deletion)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lgpd_data_subject_rights_automator safely

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

lgpd_data_subject_rights_automator Rate-limited

lgpd_data_subject_rights_automator stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lgpd_data_subject_rights_automator": {
      "limits": [
        {
          "counter": "lgpd_data_subject_rights_automator_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about lgpd_data_subject_rights_automator

What does the lgpd_data_subject_rights_automator tool do? +

Automates LGPD Data Subject Access Requests (DSARs) for legal teams, handling Brazil-specific data retention, erasure, and access workflows. Accepts user identifiers, request type (access/rectification/deletion), and optional scope filters. Returns structured response with compliance status, warnings, and source references to Brazilian LGPD and CNIL decisions. It is categorised as a Execute tool in the Mcp Knowledge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does lgpd_data_subject_rights_automator accept? +

lgpd_data_subject_rights_automator accepts 5 parameters: async, scope, urgency, requestType, userIdentifier. Required: requestType, userIdentifier. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on lgpd_data_subject_rights_automator? +

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

What risk level is lgpd_data_subject_rights_automator? +

lgpd_data_subject_rights_automator is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit lgpd_data_subject_rights_automator? +

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

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

lgpd_data_subject_rights_automator is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Knowledge, and thousands of servers like it.

This server

All 271 Mcp Knowledge tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →