Post cost estimate comments to pull requests on GitHub, GitLab, Azure Repos, or Bitbucket. Automatically updates existing comments. Requires infracost CLI to be installed and appropriate platform credentials.
AI agents use infracost_comment to create or update resources in Infracost MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Infracost MCP Server environment.
This tool creates and modifies comments on pull requests, which are reversible write operations. While it interacts with external systems, it does not delete data (Destructive), move money (Financial), or execute arbitrary code (Execute). The impact is scoped to adding or updating cost estimate comments.
From the tool's definition Tool description states it will 'Post cost estimate comments to pull requests' and 'Automatically updates existing comments', which are write operations that create or modify data on external systems (GitHub, GitLab, Azure Repos, or Bitbucket).
Attacks that exploit this kind of access
Post cost estimate comments to pull requests on GitHub, GitLab, Azure Repos, or Bitbucket. Automatically updates existing comments. Requires infracost CLI to be installed and appropriate platform credentials. It is categorised as a Write tool in the Infracost MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Infracost MCP Server MCP server in PolicyLayer and add a rule for infracost_comment: 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 Infracost MCP Server. Nothing to install.
infracost_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the infracost_comment 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 infracost_comment. 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.
infracost_comment is provided by the Infracost MCP Server MCP server (phildougherty/infracost_mcp). 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 →