Query identity registry state (merkle root, OFAC roots) for a document type
AI agents call self_get_registry_info to retrieve information from Self MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries blockchain or registry data (merkle roots, OFAC compliance roots) for a given document type. It has no side effects, does not execute code, does not modify data, and does not move funds. It is a straightforward data retrieval operation, fitting the 'Read' category.
From the tool's definition Tool name contains 'get' and description states 'Query identity registry state' — a retrieval operation with no modification or execution. Returns merkle root and OFAC roots, which are read-only state attributes.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access self_get_registry_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Self MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for self_get_registry_info:
{
"version": "1",
"default": "deny",
"tools": {
"self_get_registry_info": {}
}
}self_get_registry_info 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.
Query identity registry state (merkle root, OFAC roots) for a document type. It is categorised as a Read tool in the Self MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Self MCP Server MCP server in PolicyLayer and add a rule for self_get_registry_info: 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 Self MCP Server. Nothing to install.
self_get_registry_info 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 self_get_registry_info 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 self_get_registry_info. 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.
self_get_registry_info is provided by the Self MCP Server MCP server (selfxyz/self-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Self 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.
3 Self MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.