Search for people profiles in the company Example request: { "query": "Find people named John Doe", "filters": { "department": "Engineering", "city": "San Francisco" }, "pageSize": 10 }
AI agents call people_profile_search to retrieve information from Local without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | — | Free-text query to search people by name, title, etc. |
filters | object | — | Allowed facet fields: email, first_name, last_name, manager_email, department, title, location, city, country, state, region, business_unit, team, team_id, nick |
pageSize | integer | — | Hint to the server for how many people to return (1-100, default 10). |
Parameters from the server's own tool schema.
This tool retrieves or queries people profile data from the company's system with no side effects. It returns filtered results based on search criteria but does not create, modify, delete, or execute any operations. The low severity reflects that misuse would only expose searchable employee information without enabling destructive or financial actions.
From the tool's definition Tool name contains 'search' and description states 'Search for people profiles in the company'. The example request shows query-based retrieval with filtering parameters (department, city, pageSize) typical of read operations.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search for people profiles in the company Example request: { "query": "Find people named John Doe", "filters": { "department": "Engineering", "city": "San Francisco" }, "pageSize": 10 }. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
people_profile_search accepts 3 parameters: query, filters, pageSize. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for people_profile_search: 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 Local. Nothing to install.
people_profile_search 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 people_profile_search 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 people_profile_search. 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.
people_profile_search is provided by the Local MCP server (@gleanwork/local-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
people_profile_search is one line of Local's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →