Return the signed-in user
AI agents call admin.recent_actions 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.
The tool description indicates it returns user information (read-only retrieval). Despite the name 'recent_actions' suggesting it might return action history, the description only mentions returning the signed-in user, which is a read operation with minimal blast radius. Confidence is slightly reduced because the description doesn't fully match the tool name, suggesting possible mismatch or incomplete description.
From the tool's definition 'Return the signed-in user' — retrieves information about the current authenticated user; no side effects implied
Attacks that exploit this kind of access
Return the signed-in 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.recent_actions: 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.recent_actions 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.recent_actions 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.recent_actions. 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.recent_actions 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 →