muse_session_stats

Part of the Vibe Coding MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents use muse_session_stats 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.

// WHY ENFORCE A POLICY ON MUSE_SESSION_STATS

Without a policy, an AI agent could call muse_session_stats 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.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-muse-code-space-vibe-coding.yaml

tools:
  muse_session_stats:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Vibe Coding policy for all 15 tools.

// DETAILS

Tool Name muse_session_stats

Category Write

MCP Server Vibe Coding MCP Server

Risk Level Medium

// MORE VIBE CODING TOOLS

Destructive muse_batch Destructive muse_template Write muse_auto_tag Write muse_collect_code_context Write muse_create_session_log Write muse_export_session Write muse_generate_dev_document Write muse_normalize_for_platform

View all 15 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like muse_session_stats have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the muse_session_stats tool do? +

Provides analytics and insights about coding sessions. Actions: overview (summary stats), languages (language breakdown), timeline (activity over time), tags (tag analysis), productivity (work patterns), trends (compare periods).. 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.

How do I enforce a policy on muse_session_stats? +

Add a rule in your Intercept YAML policy under the tools section for muse_session_stats. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Vibe Coding MCP server.

What risk level is muse_session_stats? +

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

Can I rate-limit muse_session_stats? +

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

How do I block muse_session_stats completely? +

Set action: deny in the Intercept policy for muse_session_stats. 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 muse_session_stats? +

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

muse_session_stats

Enforce policies on Vibe Coding