setup_check
Check if AWS Security Agent prerequisites are configured. Verifies agent space and service role are available. If not ready, lists existing agent spaces to help with setup.
This record as markdown: /tools/aws/setup-check.md
What setup_check does on AWS
AI agents call setup_check to retrieve information from AWS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why setup_check is rated Low
The tool only reads and verifies configuration state (checks prerequisites, verifies availability, lists spaces). No data is modified, executed, or deleted. It is a purely diagnostic/informational operation.
From the tool's definition Check if AWS Security Agent prerequisites are configured. Verifies agent space and service role are available. If not ready, lists existing agent spaces to help with setup.
Attacks that exploit this kind of access
The rule that runs setup_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For setup_check, this is the rule to start with:
setup_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every setup_check call is checked against it from then on.
Questions about setup_check
Check if AWS Security Agent prerequisites are configured. Verifies agent space and service role are available. If not ready, lists existing agent spaces to help with setup. It is categorised as a Read tool in the AWS MCP Server, which means it retrieves data without modifying state.
Register the AWS MCP server in PolicyLayer and add a rule for setup_check: 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. Nothing to install.
setup_check 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 setup_check 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 setup_check. 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.
setup_check is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AWS, and thousands of servers like it.
This server
Across the catalogue