create_datasource
AI agents use create_datasource to create or update resources in AWS IoT SiteWise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS IoT SiteWise MCP Server environment.
The 'create' verb combined with 'datasource' indicates the tool creates or configures a new data source, which is a reversible write operation. While it lacks a description (lowering confidence), in the context of AWS SiteWise, creating a datasource is a Write-category operation with medium severity due to potential for misconfiguration affecting data ingestion pipelines.
From the tool's definition Tool name 'create_datasource' indicates data creation/instantiation. The context of AWS IoT SiteWise (industrial IoT data platform) suggests this creates a new data source configuration.
Attacks that exploit this kind of access
create_datasource. It is categorised as a Write tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for create_datasource: 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.
create_datasource is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_datasource 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 create_datasource. 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.
create_datasource 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.