在指定表中创建新记录
AI agents use create_record to create or update resources in AIRIOT MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AIRIOT MCP Server environment.
This tool creates or adds new data entries to tables in the IoT platform. It is a reversible modification (records can be deleted or updated), making it a Write category tool. Severity is medium because creating records could populate tables with incorrect or malicious data, but the effects are reversible. Confidence is high because the name and translated description clearly indicate a create/write operation.
From the tool's definition create_record in the AIRIOT IoT platform creates new records in specified tables. The description translates to 'create new record in specified table.' This is a data creation operation.
Attacks that exploit this kind of access
在指定表中创建新记录. It is categorised as a Write tool in the AIRIOT MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AIRIOT MCP Server MCP server in PolicyLayer and add a rule for create_record: 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.
create_record 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_record 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_record. 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_record 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 →