执行报表生成,返回报表数据
AI agents invoke execute_report to trigger actions in AIRIOT MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers report generation, which is a computational operation with side effects (resource consumption, potential data aggregation/transformation). Although not destructive or financial, it executes a process whose scope and impact depend on report parameters. In an IoT platform context, reports may query sensitive device data or trigger data processing workflows.
From the tool's definition Tool name is 'execute_report' with description stating it 'executes report generation and returns report data' (translated from Chinese: 执行报表生成,返回报表数据).
Attacks that exploit this kind of access
执行报表生成,返回报表数据. It is categorised as a Execute tool in the AIRIOT MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AIRIOT MCP Server MCP server in PolicyLayer and add a rule for execute_report: 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 AIRIOT MCP Server. Nothing to install.
execute_report is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_report 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 execute_report. 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.
execute_report is provided by the AIRIOT MCP Server MCP server (sshwsfc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →