AI agents call get_setting 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 retrieves Django configuration settings without modifying state. It is a read operation with minimal blast radius—exposing settings could leak sensitive configuration, but the tool itself performs no destructive, execute, or financial actions. Low severity reflects that information disclosure from settings is contextual; destructive operations would require separate Execute or Destructive tools.
From the tool's definition Tool name 'get_setting' indicates retrieval of configuration values. Server description emphasizes 'read-only resources' and 'project configuration' access.
Documented attack patterns abuse exactly the kind of access get_setting 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_setting:
{
"version": "1",
"default": "deny",
"tools": {
"get_setting": {}
}
}get_setting 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_setting. 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_setting: 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_setting 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_setting 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_setting. 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_setting 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.