Create a new object through the consumer
AI agents use admin.create to create or update resources in Django Admin Mcp Api — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Django Admin Mcp Api environment.
This tool creates new objects, which is a reversible write operation. Severity is high because it creates data within an authenticated Django admin context, potentially affecting multiple system records depending on the model and consumer permissions. It is not Destructive (no deletion), Execute (not arbitrary code execution), or Financial (no explicit money movement).
From the tool's definition Tool name 'admin.create' and description 'Create a new object through the consumer' indicate creation of new data. The server exposes Django admin ModelAdmin functionality with form validation and session authentication.
Attacks that exploit this kind of access
Create a new object through the consumer. It is categorised as a Write tool in the Django Admin Mcp Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Django Admin Mcp Api MCP server in PolicyLayer and add a rule for admin.create: 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.create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the admin.create 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.create. 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.create 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 →