searchUsersByQueryWithId

Retrieves the users for the given search criteria and pagination.

SERVERFusionauth SOURCE@fusionauth/mcp-api
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/io-fusionauth-mcp-api/searchusersbyquerywithid.md

What searchUsersByQueryWithId does on Fusionauth

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

Why searchUsersByQueryWithId is rated Low

This tool performs a search query to retrieve user data based on provided criteria. It has no capability to modify, delete, or execute operations—it only fetches and returns existing user information. This is a standard Read operation with minimal security risk, assuming the search is appropriately scoped by the caller's permissions.

From the tool's definition Tool description states it 'Retrieves the users for the given search criteria and pagination.' The verb 'Retrieves' and the query-based nature indicate a read-only operation with no data modification or side effects.

Questions about searchUsersByQueryWithId

What does the searchUsersByQueryWithId tool do? +

Retrieves the users for the given search criteria and pagination. It is categorised as a Read tool in the Fusionauth MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on searchUsersByQueryWithId? +

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

What risk level is searchUsersByQueryWithId? +

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

Can I rate-limit searchUsersByQueryWithId? +

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

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

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

More on Fusionauth, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Fusionauth's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.