manage_person

Full CRUD for people/contacts: create, read, update, delete, enrich, and view communication history.

SERVERAdrata SOURCE@adrata/adrata-mcp

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/adrata-adrata-mcp/manage-person.md

WHAT IT DOES

What manage_person does on Adrata

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

RISK

Why manage_person is rated Medium

An AI agent can call manage_person faster than any human can review: one bad instruction and it creates or modifies resources in Adrata by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs manage_person safely

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

manage_person Rate-limited

manage_person 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": {
    "manage_person": {
      "limits": [
        {
          "counter": "manage_person_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 Adrata, apply this rule, and every manage_person call is checked against it from then on.

FAQ

Questions about manage_person

What does the manage_person tool do? +

Full CRUD for people/contacts: create, read, update, delete, enrich, and view communication history. It is categorised as a Write tool in the Adrata MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_person? +

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

What risk level is manage_person? +

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

Can I rate-limit manage_person? +

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

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

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

KEEP EXPLORING

More on Adrata, and thousands of servers like it.

This server

All 278 Adrata tools →

Across the catalogue

The MCP Attack Database →

Guides

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