browser_type
AI agents call browser_type as a supporting operation in AWS IoT SiteWise MCP Server workflows.
The tool name 'browser_type' does not clearly map to any obvious AWS IoT SiteWise operation, and the description is empty. 'browser_type' could suggest a browser automation action (typing into a browser field), which would be Execute category, but this is highly speculative given the IoT SiteWise context. Without a description, confidence is very low and categorizing as Other is most appropriate.
From the tool's definition Tool name is 'browser_type' but description is empty or uninformative; cannot determine what the tool does from available information.
Attacks that exploit this kind of access
browser_type. It is categorised as a Other tool in the AWS IoT SiteWise MCP Server MCP Server, which means it performs auxiliary operations.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for browser_type: 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.
browser_type is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the browser_type 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 browser_type. 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.
browser_type 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.