search_sloneek_users

// WHEN AI AGENTS USE THIS TOOL

AI agents call search_sloneek_users to retrieve information from Sloneek MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON SEARCH_SLONEEK_USERS

Even though search_sloneek_users only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

souky-byte-sloneek-mcp.yaml

tools:
  search_sloneek_users:
    rules:
      - action: allow

See the full Sloneek MCP Server policy for all 12 tools.

// DETAILS

Tool Name search_sloneek_users

Category Read

MCP Server Sloneek MCP Server MCP Server

Risk Level Low

// MORE SLONEEK MCP SERVER TOOLS

Write add_bonus_to_employees Write create_sloneek_absence Write create_sloneek_survey Read get_sloneek_absence_options Read get_sloneek_birthdays Read get_sloneek_salary_history Read get_sloneek_user_personal_information Read get_sloneek_user_timeline

View all 12 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like search_sloneek_users have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the search_sloneek_users tool do? +

search_sloneek_users. It is categorised as a Read tool in the Sloneek MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_sloneek_users? +

Add a rule in your Intercept YAML policy under the tools section for search_sloneek_users. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Sloneek MCP Server MCP server.

What risk level is search_sloneek_users? +

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

Can I rate-limit search_sloneek_users? +

Yes. Add a rate_limit block to the search_sloneek_users rule in your Intercept 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_sloneek_users completely? +

Set action: deny in the Intercept policy for search_sloneek_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_sloneek_users? +

search_sloneek_users is provided by the Sloneek MCP Server MCP server (souky-byte/sloneek-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Sloneek MCP Server