describe-engine-default-parameters
AI agents call describe-engine-default-parameters 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 naming convention suggests this tool queries and returns default engine parameters (likely database or compute engine settings). This is a read-only operation that retrieves information without side effects. Confidence is moderate (0.75) rather than high because the description is empty, leaving some ambiguity about the exact parameters returned and scope of access.
From the tool's definition Tool name 'describe-engine-default-parameters' contains the verb 'describe', which typically retrieves or queries configuration parameters without modification.
Attacks that exploit this kind of access
describe-engine-default-parameters. 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 describe-engine-default-parameters: 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.
describe-engine-default-parameters 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 describe-engine-default-parameters 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 describe-engine-default-parameters. 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.
describe-engine-default-parameters 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.