setup_cross_account_access · AWS

WHAT IT DOES

What setup_cross_account_access does on AWS_CloudGuardMCP

AI agents use setup_cross_account_access to create or update resources in AWS_CloudGuardMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS_CloudGuardMCP environment.

WHY IT NEEDS A POLICY

Why setup_cross_account_access needs a policy

The tool modifies AWS account permissions and access configurations, which affects authentication and authorization boundaries. This is categorized as Write rather than Execute because it configures infrastructure state rather than triggering transient operations.

From the tool's definition Tool performs 'setup' of 'cross-account access' which modifies AWS IAM/access control configuration. This is a reversible configuration change that creates or modifies access policies and roles.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_cross_account_access Rate-limited

setup_cross_account_access 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": {
    "setup_cross_account_access": {
      "limits": [
        {
          "counter": "setup_cross_account_access_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 AWS_CloudGuardMCP, so you can run agents against it safely.

FAQ

Questions about setup_cross_account_access

What does the setup_cross_account_access tool do? +

Sets up cross-account access for CloudWatch monitoring. It is categorised as a Write tool in the AWS_CloudGuardMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on setup_cross_account_access? +

Register the AWS_CloudGuard MCP server in PolicyLayer and add a rule for setup_cross_account_access: 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 AWS_CloudGuardMCP. Nothing to install.

What risk level is setup_cross_account_access? +

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

Can I rate-limit setup_cross_account_access? +

Yes. Add a rate_limit block to the setup_cross_account_access 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 setup_cross_account_access completely? +

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

setup_cross_account_access is provided by the AWS_CloudGuard MCP server (madhurprash/aws_cloudguardmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.