シナリオを部分更新する。fields は変更したいフィールドのみ含めればよい
AI agents use update_scenario to create or update resources in Poranos Mcp Ainpc — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Poranos Mcp Ainpc environment.
The tool creates or modifies data (a scenario) in a way that is reversible—updates can be overwritten or reverted. This is characteristic of Write operations. While it affects NPC scenario configurations that may influence AI behavior, the modification itself is not destructive (data is not deleted/purged) and not Execute (it does not run code or trigger external operations).
From the tool's definition Tool name 'update_scenario' and description indicating partial update of scenario fields ('シナリオを部分更新する' = 'Partially update a scenario'). This modifies existing data reversibly.
Attacks that exploit this kind of access
シナリオを部分更新する。fields は変更したいフィールドのみ含めればよい. It is categorised as a Write tool in the Poranos Mcp Ainpc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Poranos Mcp Ainpc MCP server in PolicyLayer and add a rule for update_scenario: 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 Poranos Mcp Ainpc. Nothing to install.
update_scenario 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 update_scenario 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 update_scenario. 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.
update_scenario is provided by the Poranos Mcp Ainpc MCP server (kkoba23/poranos-mcp-ainpc). 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 →