get_roles_for_service
AI agents call get_roles_for_service to retrieve information from AWS IoT SiteWise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to fetch or list IAM roles assigned to a service, which is a read-only operation with no side effects. It retrieves existing data without modification, deletion, or execution capabilities. The lack of description lowers confidence slightly, but the naming convention strongly suggests a simple metadata query.
From the tool's definition Tool name 'get_roles_for_service' indicates a retrieval operation querying roles associated with a service. No description provided, but the naming pattern is consistent with AWS IAM/service metadata query tools.
Attacks that exploit this kind of access
get_roles_for_service. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for get_roles_for_service: 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 IoT SiteWise MCP Server. Nothing to install.
get_roles_for_service 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 get_roles_for_service 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 get_roles_for_service. 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.
get_roles_for_service is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.