Run one of the model
AI agents invoke admin.action to trigger actions in Django Admin Mcp Api. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Admin actions in Django are custom callables attached to ModelAdmin that execute business logic on model instances—ranging from data transformations to external API calls to report generation. While bound by Django's permission system (inherited from the server's session auth), the execution effects depend entirely on which action is invoked and what arguments are passed, making this an Execute risk.
From the tool's definition Tool name 'admin.action' described as 'Run one of the model' - the word 'Run' indicates execution of code or operations.
Attacks that exploit this kind of access
Run one of the model. It is categorised as a Execute tool in the Django Admin Mcp Api MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Django Admin Mcp Api MCP server in PolicyLayer and add a rule for admin.action: 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.action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the admin.action 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.action. 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.action 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →