find_or_create_person

Find a person by email or name+company, or create them if they don\

SERVERAdrata SOURCE@adrata/adrata-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-adrata-mcp/find-or-create-person.md

WHAT IT DOES

What find_or_create_person does on Adrata

AI agents call find_or_create_person to retrieve information from Adrata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why find_or_create_person is rated Low

Even though find_or_create_person only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_or_create_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 find_or_create_person, this is the rule to start with:

find_or_create_person Allowed

find_or_create_person is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_or_create_person": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about find_or_create_person

What does the find_or_create_person tool do? +

Find a person by email or name+company, or create them if they don\. It is categorised as a Read tool in the Adrata MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_or_create_person? +

Register the Adrata MCP server in PolicyLayer and add a rule for find_or_create_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 find_or_create_person? +

find_or_create_person is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_or_create_person? +

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

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

find_or_create_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

Roll out MCP under one policy →Data exfiltration →MCP token cost →