get_my_profile

THE RISK

Low Risk

Why get_my_profile needs a policy

This tool retrieves user profile information without modifying, deleting, or executing operations. It has minimal blast radius as it only accesses existing data. Severity is low because profile retrieval is a standard read operation, though sensitivity of the data itself is mitigated by the fact that it retrieves 'your' (the authenticated user's) own profile rather than arbitrary user data.

From the tool's definition Tool name 'get_my_profile' and description 'Get your profile' indicate a retrieval operation with no modification or deletion. The verb 'get' and context of reading profile data confirm this is a query operation.

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

POLICY

How to control get_my_profile

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_my_profile:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_my_profile": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Inoyu Apache Unomi MCP Server tools

Write create_scope Create a new Unomi scope Write update_consent Update a user Write update_my_profile Update properties of your profile using environment-provided ID Read get_consent Get specific consent information for a profile Read get_profile Get a specific Unomi profile by ID Read get_tenant_info Get information about the current tenant (V3 only) Read list_consents List all consents for a profile with optional filtering Read search_profiles Search Unomi profiles

All 9 Inoyu Apache Unomi MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_my_profile

What does the get_my_profile tool do? +

Get your profile using environment-provided IDs. 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 get_my_profile? +

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

What risk level is get_my_profile? +

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

Can I rate-limit get_my_profile? +

Yes. Add a rate_limit block to the get_my_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.

How do I block get_my_profile completely? +

Set action: deny in the PolicyLayer policy for get_my_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.

What MCP server provides get_my_profile? +

get_my_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.

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.

CHECK YOUR STACK →