get_patient_studies
AI agents call get_patient_studies 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 follows standard read operation naming conventions ('get_'). Although the description is empty—which reduces confidence slightly—the semantic meaning of 'get_patient_studies' clearly suggests querying or retrieving patient study records without side effects. This is consistent with Read category operations that retrieve data. No evidence of modification, deletion, execution, or financial impact.
From the tool's definition Tool name 'get_patient_studies' indicates retrieval of patient study data with no modification suggested. The description is empty, but the 'get_' prefix is a strong indicator of read-only retrieval operations.
Attacks that exploit this kind of access
get_patient_studies. 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_patient_studies: 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_patient_studies 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_patient_studies 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_patient_studies. 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_patient_studies 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.