memory_update_intensity · Wasurenagusa MCP: Risk & Policy

Q: What does the memory_update_intensity tool do?

既存メモリエントリのintensity（重要度）だけを変更する。 ピン留め運用に使う: intensity 6以上を設定するとcontext注入で最優先される。 memory_searchで取得したIDを指定すること。. It is categorised as a Write tool in the Wasurenagusa MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

WHAT IT DOES

What memory_update_intensity does on Wasurenagusa

AI agents use memory_update_intensity to create or update resources in Wasurenagusa — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wasurenagusa environment.

WHY IT NEEDS A POLICY

Why memory_update_intensity needs a policy

This tool modifies metadata (intensity/priority) of existing memory records without deleting them, which is reversible. It falls under Write (modifies data) rather than Read (query-only) or Destructive (irreversible deletion).

From the tool's definition Tool name 'memory_update_intensity' and description indicates it modifies ('change', '変更する') an existing memory entry's 'intensity' field.

Attacks that exploit this kind of access

Questions about memory_update_intensity

What does the memory_update_intensity tool do? +

既存メモリエントリのintensity（重要度）だけを変更する。ピン留め運用に使う: intensity 6以上を設定するとcontext注入で最優先される。 memory_searchで取得したIDを指定すること。. It is categorised as a Write tool in the Wasurenagusa MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_update_intensity? +

Register the Wasurenagusa MCP server in PolicyLayer and add a rule for memory_update_intensity: 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.

What risk level is memory_update_intensity? +

memory_update_intensity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit memory_update_intensity? +

Yes. Add a rate_limit block to the memory_update_intensity 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.

How do I block memory_update_intensity completely? +

Set action: deny in the PolicyLayer policy for memory_update_intensity. 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.

What MCP server provides memory_update_intensity? +

memory_update_intensity 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.