List recent validation decisions and architectural choices the AI has made in this project. Returns time-descending rows.
AI agents call get_recent_decisions to retrieve information from Carto 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 and displays historical data about architectural decisions made by the AI. It has no side effects, does not modify or delete data, does not execute code, and does not trigger external operations. It is purely informational, fitting the Read category.
From the tool's definition Tool name is 'get_recent_decisions' with description stating it 'List[s] recent validation decisions' - this is a retrieval operation returning historical records with no modification, deletion, or execution of code/commands.
Documented attack patterns abuse exactly the kind of access get_recent_decisions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Carto MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_recent_decisions:
{
"version": "1",
"default": "deny",
"tools": {
"get_recent_decisions": {}
}
}get_recent_decisions 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.
List recent validation decisions and architectural choices the AI has made in this project. Returns time-descending rows. It is categorised as a Read tool in the Carto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Carto MCP Server MCP server in PolicyLayer and add a rule for get_recent_decisions: 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 Carto MCP Server. Nothing to install.
get_recent_decisions 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_recent_decisions 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_recent_decisions. 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_recent_decisions is provided by the Carto MCP Server MCP server (theanshsonkar/carto). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 Carto MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 Carto MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.