Get detailed information about a specific terminology.
AI agents call get_terminology 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 retrieves or queries information about a terminology resource without altering, deleting, or executing operations. It is a straightforward read operation that returns data to the user. The blast radius of misuse is minimal—an AI agent calling this tool would only access terminology metadata, which carries no destructive, financial, or executable consequences.
From the tool's definition Tool name 'get_terminology' and description 'Get detailed information about a specific terminology' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
Get detailed information about a specific terminology. 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_terminology: 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_terminology 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_terminology 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_terminology. 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_terminology 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.