search-users

Search for users in Descope project

SERVERDescope MCP Server SOURCEdescope-sample-apps/descope-mcp-server-stdio

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/descope-sample-apps-descope-mcp-server/search-users.md

WHAT IT DOES

What search-users does on Descope MCP Server

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

RISK

Why search-users is rated Low

This tool performs a search/retrieval operation with no side effects. It queries existing user data from the Descope project but does not create, modify, or delete any data. The blast radius of misuse is limited to potential exposure of user information already in the system, making it a Read-category tool with low severity.

From the tool's definition Tool name 'search-users' and description 'Search for users in Descope project' indicate a query operation that retrieves user data without modifying or deleting it.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search-users safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Descope MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search-users, this is the rule to start with:

search-users Allowed

search-users is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search-users": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Descope MCP Server, apply this rule, and every search-users call is checked against it from then on.

FAQ

Questions about search-users

What does the search-users tool do? +

Search for users in Descope project. It is categorised as a Read tool in the Descope MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search-users? +

Register the Descope MCP Server 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 Descope MCP Server. Nothing to install.

What risk level is search-users? +

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

Can I rate-limit search-users? +

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.

How do I block search-users completely? +

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.

What MCP server provides search-users? +

search-users is provided by the Descope MCP Server MCP server (descope-sample-apps/descope-mcp-server-stdio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Descope MCP Server, and thousands of servers like it.

This server

All 4 Descope MCP Server tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →