get_serverless_templates
AI agents call get_serverless_templates 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.
The tool name suggests it retrieves or fetches serverless templates without modifying them. No parameters or description provided to suggest mutation, deletion, or execution of arbitrary code. Following the 'Read' category definition for retrieval operations, this is classified as Read. Confidence is reduced from high to medium-low due to the empty description, which leaves some ambiguity about actual behavior.
From the tool's definition Tool name 'get_serverless_templates' indicates retrieval of template data. Description is empty, limiting confidence.
Attacks that exploit this kind of access
get_serverless_templates. 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_serverless_templates: 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_serverless_templates 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_serverless_templates 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_serverless_templates. 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_serverless_templates 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.