Get comprehensive project information including Python environment and Django configuration.
AI agents call get_project_info to retrieve information from Django MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only fetches and returns data about the Django project structure and configuration. It has no side effects, cannot modify state, and presents no blast radius if invoked by an AI agent. It is a straightforward read operation consistent with the Read category definition (retrieves or queries data; no side effects).
From the tool's definition Tool name 'get_project_info' and description explicitly states it retrieves/queries 'comprehensive project information including Python environment and Django configuration' with no mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_project_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Django MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_project_info": {}
}
}get_project_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.
Get comprehensive project information including Python environment and Django configuration. It is categorised as a Read tool in the Django MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Django MCP Server MCP server in PolicyLayer and add a rule for get_project_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 Django MCP Server. Nothing to install.
get_project_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 get_project_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 get_project_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.
get_project_info is provided by the Django MCP Server MCP server (joshuadavidthomas/mcp-django). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Django 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.
13 Django MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.