config（設定情報）とdont（やってはいけないこと）を一括取得する。 通常はSessionStart Hookで自動注入されるため、手動で呼ぶ必要は少ない。 セッション途中でコンテキストを再確認したい場合に使用。
AI agents call memory_get_context to retrieve information from Wasurenagusa without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
memory_get_context performs a read-only query of stored project rules, decisions, and constraints. It retrieves existing data for context awareness rather than creating, modifying, deleting, or executing actions. While the server itself performs autonomous tasks via Gemini, this specific tool only fetches information.
From the tool's definition Tool retrieves configuration (config) and constraint information (dont) without modification. Description states it 'gets in bulk' (一括取得する) configuration and rules. This is a pure data retrieval operation with no side effects.
Attacks that exploit this kind of access
config（設定情報）とdont（やってはいけないこと）を一括取得する。 通常はSessionStart Hookで自動注入されるため、手動で呼ぶ必要は少ない。 セッション途中でコンテキストを再確認したい場合に使用。. It is categorised as a Read tool in the Wasurenagusa MCP Server, which means it retrieves data without modifying state.
Register the Wasurenagusa MCP server in PolicyLayer and add a rule for memory_get_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 Wasurenagusa. Nothing to install.
memory_get_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 memory_get_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 memory_get_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.
memory_get_context is provided by the Wasurenagusa MCP server (tsutushi0628/wasurenagusa-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 →