特定のサービスのアーキテクチャコンテキストを取得します。
AI agents call waroom_get_service_architecture_context to retrieve information from Waroom MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves architecture context information about a service with no side effects. It is a read-only query operation that retrieves data from the Waroom API. The blast radius of misuse is minimal—an agent could only access architectural documentation/metadata, not trigger incidents, modify data, or execute operations.
From the tool's definition Tool name contains 'get_' prefix and description states 'retrieve' (特定のサービスのアーキテクチャコンテキストを取得します translates to 'retrieve the architecture context of a specific service'). No modification, deletion, or execution of operations is indicated.
Attacks that exploit this kind of access
特定のサービスのアーキテクチャコンテキストを取得します。. It is categorised as a Read tool in the Waroom MCP MCP Server, which means it retrieves data without modifying state.
Register the Waroom MCP server in PolicyLayer and add a rule for waroom_get_service_architecture_context: 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 Waroom MCP. Nothing to install.
waroom_get_service_architecture_context 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 waroom_get_service_architecture_context 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 waroom_get_service_architecture_context. 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.
waroom_get_service_architecture_context is provided by the Waroom MCP server (topotal/waroom-mcp). 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 →