List every model registered on the AdminSite that the authenticated user
AI agents call admin.registry to retrieve information from Django Admin Mcp Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists metadata about available Django admin models. It performs a query operation constrained by user authentication permissions, returning information only about models the user can access. There are no mutations, deletions, executions, or financial implications. The read of admin metadata is a low-risk informational query.
From the tool's definition Tool name 'admin.registry' and description 'List every model registered on the AdminSite' indicate a read-only enumeration/listing operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every model registered on the AdminSite that the authenticated user. It is categorised as a Read tool in the Django Admin Mcp Api MCP Server, which means it retrieves data without modifying state.
Register the Django Admin Mcp Api MCP server in PolicyLayer and add a rule for admin.registry: 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 Django Admin Mcp Api. Nothing to install.
admin.registry 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 admin.registry 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 admin.registry. 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.
admin.registry is provided by the Django Admin Mcp Api MCP server (martincastroalvarez/django-admin-mcp-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
admin.registry is one line of Django Admin Mcp Api's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →