Low Risk

get_identity_core

Retrieve the current identity model and core memory clusters

How to control get_identity_core ↓

What get_identity_core does on AGI MCP Server

AI agents call get_identity_core to retrieve information from AGI 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 get_identity_core needs a policy

This is a retrieval operation that accesses stored identity and memory data. It performs a query with no mutations, deletions, or external side effects. Even though the data retrieved relates to AI identity/memory state, the tool itself is read-only and poses minimal risk of misuse—an agent cannot cause damage by retrieving this information.

From the tool's definition Tool name contains 'get_' and description uses 'Retrieve', both indicating data retrieval without side effects. The tool queries 'current identity model and core memory clusters' without modifying or deleting data.

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

How to control get_identity_core

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

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

get_identity_core 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 AGI 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 get_identity_core

What does the get_identity_core tool do? +

Retrieve the current identity model and core memory clusters. It is categorised as a Read tool in the AGI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_identity_core? +

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

What risk level is get_identity_core? +

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

Can I rate-limit get_identity_core? +

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

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

get_identity_core is provided by the AGI MCP Server MCP server (quixiai/agi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AGI MCP Server tool call.

Start from AGI 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.

24 AGI 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.