Low Risk

search_profiles

Search Unomi profiles

How to control search_profiles ↓

What search_profiles does on Inoyu Apache Unomi MCP Server

AI agents call search_profiles to retrieve information from Inoyu Apache Unomi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_profiles needs a policy

This tool searches or queries existing user profile data without creating, modifying, or deleting records. It retrieves information for inspection purposes only, making it a Read category tool with low severity since the blast radius of misuse (returning profile data) is limited to information disclosure rather than data manipulation or destruction.

From the tool's definition Tool name 'search_profiles' and description 'Search Unomi profiles' indicate a query/retrieval operation with no modification or deletion of data.

Documented attack patterns abuse exactly the kind of access search_profiles gives an agent:

How to control search_profiles

PolicyLayer is an MCP gateway — it sits between your AI agents and Inoyu Apache Unomi MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_profiles:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_profiles": {}
  }
}

search_profiles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Inoyu Apache Unomi MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_profiles

What does the search_profiles tool do? +

Search Unomi profiles. It is categorised as a Read tool in the Inoyu Apache Unomi MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_profiles? +

Register the Inoyu Apache Unomi MCP Server MCP server in PolicyLayer and add a rule for search_profiles: 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 Inoyu Apache Unomi MCP Server. Nothing to install.

What risk level is search_profiles? +

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

Can I rate-limit search_profiles? +

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

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

search_profiles is provided by the Inoyu Apache Unomi MCP Server MCP server (inoyu-dev/inoyu-mcp-unomi-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Inoyu Apache Unomi MCP Server tool call.

Start from Inoyu Apache Unomi MCP Server, 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.

9 Inoyu Apache Unomi MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.