Fetch recent deploy records from SQLite, most-recent-first.
AI agents call get_deploy_history to retrieve information from Mcp Deploy Intel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical deployment records from a database and returns them in reverse chronological order. It performs a read-only operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal—an attacker gains visibility into deployment history but cannot alter systems or trigger actions.
From the tool's definition Tool name and description: 'Fetch recent deploy records from SQLite, most-recent-first' — explicitly a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Fetch recent deploy records from SQLite, most-recent-first. It is categorised as a Read tool in the Mcp Deploy Intel MCP Server, which means it retrieves data without modifying state.
Register the Mcp Deploy Intel MCP server in PolicyLayer and add a rule for get_deploy_history: 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 Mcp Deploy Intel. Nothing to install.
get_deploy_history 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_deploy_history 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_deploy_history. 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_deploy_history is provided by the Mcp Deploy Intel MCP server (vellankikoti/mcp-deploy-intel). 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 →