List all inline policies for an IAM role.
AI agents call list_role_policies to retrieve information from Amazon Redshift MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing IAM role policies. It performs no creation, modification, deletion, or execution of code/commands. While the information returned could potentially be sensitive (revealing security configurations), the tool itself is a pure read operation with minimal blast radius if misused by an AI agent—it merely exposes what policies are already attached to a role.
From the tool's definition Tool name 'list_role_policies' and description 'List all inline policies for an IAM role' indicate a retrieval operation with no side effects. The verb 'list' is a classic Read operation that queries and returns information without modifying or deleting data.
Documented attack patterns abuse exactly the kind of access list_role_policies gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Redshift MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_role_policies:
{
"version": "1",
"default": "deny",
"tools": {
"list_role_policies": {}
}
} list_role_policies is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all inline policies for an IAM role. It is categorised as a Read tool in the Amazon Redshift MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon Redshift MCP Server MCP server in PolicyLayer and add a rule for list_role_policies: 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 Amazon Redshift MCP Server. Nothing to install.
list_role_policies 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 list_role_policies 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 list_role_policies. 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.
list_role_policies is provided by the Amazon Redshift MCP Server MCP server (awslabs.redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Redshift MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Amazon Redshift MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.