find_person
Find person by name with fuzzy search (handles typos, accents, case). Searches local DB + WhatsApp. Args: search (name), instance_name. Returns: matching contacts sorted by relevance.
This record as markdown: /tools/namastexlabs-automagik-tools/find-person.md
What find_person does on Automagik Tools
AI agents call find_person to retrieve information from Automagik Tools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why find_person is rated Low
The tool retrieves and searches existing contact information using fuzzy matching but does not create, modify, delete, or execute any side effects. It returns contact data matching search criteria, which is purely informational lookup functionality. The low severity reflects that unauthorized use would only expose contact information already stored in accessible databases, with no ability to alter or destroy data.
From the tool's definition Tool performs a 'Find person by name with fuzzy search' that 'Searches local DB + WhatsApp' and 'Returns: matching contacts sorted by relevance.' This is a read-only query operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs find_person safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Automagik Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_person, this is the rule to start with:
find_person is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Automagik Tools, apply this rule, and every find_person call is checked against it from then on.
Questions about find_person
Find person by name with fuzzy search (handles typos, accents, case). Searches local DB + WhatsApp. Args: search (name), instance_name. Returns: matching contacts sorted by relevance. It is categorised as a Read tool in the Automagik Tools MCP Server, which means it retrieves data without modifying state.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for find_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 Automagik Tools. Nothing to install.
find_person is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the find_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.
Set action: deny in the PolicyLayer policy for find_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.
find_person is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Automagik Tools, and thousands of servers like it.
This server
Across the catalogue