AI agents call get_profile 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.
This tool retrieves a user profile by identifier. While retrieval of PII or sensitive user data carries medium severity risk if exposed to an AI agent without proper access controls (potential for unauthorized data access or privacy violations), the tool itself performs only a read operation with no side effects or data mutation. It is firmly in the Read category, not higher.
From the tool's definition Tool name 'get_profile' and description 'Get a specific Unomi profile by ID' indicate data retrieval with no modification. The verb 'Get' and absence of language like 'create', 'update', 'delete', or 'modify' confirm read-only semantics.
Documented attack patterns abuse exactly the kind of access get_profile gives an agent:
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 get_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_profile": {}
}
}get_profile is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a specific Unomi profile by ID. It is categorised as a Read tool in the Inoyu Apache Unomi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Inoyu Apache Unomi MCP Server MCP server in PolicyLayer and add a rule for get_profile: 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.
get_profile 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 get_profile 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 get_profile. 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.
get_profile 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.
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.