searchUsersByQueryWithId
Retrieves the users for the given search criteria and pagination.
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.
Attacks that exploit this kind of access
The rule that runs searchUsersByQueryWithId safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fusionauth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For searchUsersByQueryWithId, this is the rule to start with:
searchUsersByQueryWithId 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 Fusionauth, apply this rule, and every searchUsersByQueryWithId call is checked against it from then on.
Questions about searchUsersByQueryWithId
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.
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.
searchUsersByQueryWithId 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 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.
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.
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.
This server
Across the catalogue