Manages vibe coding session history. Save, retrieve, search, and manage past coding sessions with their code contexts and design decisions.
High parameter count (15 properties)
Part of the Vibe Coding MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use muse_session_history to create or modify resources in Vibe Coding. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call muse_session_history repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Vibe Coding.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
muse_session_history:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Vibe Coding policy for all 15 tools.
Agents calling write-class tools like muse_session_history have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Manages vibe coding session history. Save, retrieve, search, and manage past coding sessions with their code contexts and design decisions.. It is categorised as a Write tool in the Vibe Coding MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for muse_session_history. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Vibe Coding MCP server.
muse_session_history 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 muse_session_history rule in your Intercept 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 Intercept policy for muse_session_history. 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.
muse_session_history is provided by the Vibe Coding MCP server (vibe-coding-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept