Create a new scene with defined device states.
AI agents use create_scene to create or update resources in MCP Personal Assistant Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Personal Assistant Agent environment.
This tool creates new smart home scenes (groupings of device states), which is a reversible write operation. While it modifies the smart home configuration, the effect is non-destructive and can be undone or modified later. The severity is medium because misconfiguration could affect home automation but lacks the irreversibility of destructive operations or the financial impact of payment tools.
From the tool's definition Tool name 'create_scene' and description 'Create a new scene with defined device states' indicate creation of new configuration objects that control smart home devices.
Documented attack patterns abuse exactly the kind of access create_scene gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Personal Assistant Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for create_scene:
{
"version": "1",
"default": "deny",
"tools": {
"create_scene": {
"limits": [
{
"counter": "create_scene_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_scene stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new scene with defined device states. It is categorised as a Write tool in the MCP Personal Assistant Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Personal Assistant Agent MCP server in PolicyLayer and add a rule for create_scene: 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 MCP Personal Assistant Agent. Nothing to install.
create_scene 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_scene 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_scene. 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_scene is provided by the MCP Personal Assistant Agent MCP server (zhangzhongnan928/mcp-pa-ai-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Personal Assistant Agent, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 MCP Personal Assistant Agent tools catalogued and risk-classified — across an index of 43,000+ MCP servers.