Search for users in the organization by name or email. Use to find a new owner for an agent.
AI agents call search_users to retrieve information from Agent 365 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search/lookup operation against user data in the organization directory. While it accesses user information (a potentially sensitive read), it retrieves data without side effects and does not modify, delete, or execute anything. The stated purpose is to find a new owner for an agent, which is a read-only precursor to other operations.
From the tool's definition Tool description states 'Search for users in the organization by name or email' — a straightforward query operation with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access search_users gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent 365, and nothing reaches the server without passing your rules. This is the rule we recommend for search_users:
{
"version": "1",
"default": "deny",
"tools": {
"search_users": {}
}
}search_users is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for users in the organization by name or email. Use to find a new owner for an agent. It is categorised as a Read tool in the Agent 365 MCP Server, which means it retrieves data without modifying state.
Register the Agent 365 MCP server in PolicyLayer and add a rule for search_users: 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 Agent 365. Nothing to install.
search_users 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 search_users 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 search_users. 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.
search_users is provided by the Agent 365 MCP server (ramakrishnan24689/agent365-mcpapp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent 365, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Agent 365 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.