infracost_cloud_update_tagging_policy

WHAT IT DOES

What infracost_cloud_update_tagging_policy does on Infracost MCP Server

AI agents use infracost_cloud_update_tagging_policy 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.

WHY IT NEEDS A POLICY

Why infracost_cloud_update_tagging_policy needs a policy

This tool modifies existing tagging policies in Infracost Cloud, which are governance controls applied to pull requests and infrastructure validation. While reversible (policies can be updated again or deleted), the changes affect organizational compliance and infrastructure validation workflows.

From the tool's definition 'Update tagging policies' and 'allowed tag values for validation in pull requests' indicate modification of configuration policies that control governance rules across infrastructure deployments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

infracost_cloud_update_tagging_policy Rate-limited

infracost_cloud_update_tagging_policy stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "infracost_cloud_update_tagging_policy": {
      "limits": [
        {
          "counter": "infracost_cloud_update_tagging_policy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Infracost MCP Server, so you can run agents against it safely.

FAQ

Questions about infracost_cloud_update_tagging_policy

What does the infracost_cloud_update_tagging_policy tool do? +

Update tagging policies in Infracost Cloud with allowed tag values for validation in pull requests. Requires INFRACOST_SERVICE_TOKEN environment variable. 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.

How do I enforce a policy on infracost_cloud_update_tagging_policy? +

Register the Infracost MCP Server MCP server in PolicyLayer and add a rule for infracost_cloud_update_tagging_policy: 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.

What risk level is infracost_cloud_update_tagging_policy? +

infracost_cloud_update_tagging_policy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit infracost_cloud_update_tagging_policy? +

Yes. Add a rate_limit block to the infracost_cloud_update_tagging_policy 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.

How do I block infracost_cloud_update_tagging_policy completely? +

Set action: deny in the PolicyLayer policy for infracost_cloud_update_tagging_policy. 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.

What MCP server provides infracost_cloud_update_tagging_policy? +

infracost_cloud_update_tagging_policy 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.