シナリオの編集履歴を返す (最新版が先頭)。
AI agents call get_scenario_versions to retrieve information from Poranos Mcp Ainpc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and displays version history data about scenarios. It performs a read-only query operation that does not create, modify, delete, or execute any actions. The Japanese description confirms it 'returns scenario edit history,' which is purely informational access. No data is altered, no code is executed, and no irreversible changes occur.
From the tool's definition Tool name 'get_scenario_versions' and description indicate it returns edit history ('シナリオの編集履歴を返す') in reverse chronological order. This is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
シナリオの編集履歴を返す (最新版が先頭)。. It is categorised as a Read tool in the Poranos Mcp Ainpc MCP Server, which means it retrieves data without modifying state.
Register the Poranos Mcp Ainpc MCP server in PolicyLayer and add a rule for get_scenario_versions: 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.
get_scenario_versions 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 get_scenario_versions 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 get_scenario_versions. 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.
get_scenario_versions 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 →