start_monitoring · MMI Architecture Analyzer MCP

WHAT IT DOES

What start_monitoring does on MMI Architecture Analyzer

AI agents invoke start_monitoring to trigger actions in MMI Architecture Analyzer. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why start_monitoring needs a policy

This tool invokes automated background execution with side effects (file system watching, continuous analysis triggers, persistent data storage). It is not merely querying data (Read), nor is it irreversible (Destructive). While it modifies stored data (score history), the primary action is triggering execution of monitoring processes.

From the tool's definition The tool 'start_monitoring' executes continuous background monitoring operations that automatically trigger analysis on file changes and stores data persistently ('Watches .cs files and automatically analyzes on changes. Stores score history over time').

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_monitoring Rate-limited

start_monitoring stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_monitoring": {
      "limits": [
        {
          "counter": "start_monitoring_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MMI Architecture Analyzer, so you can run agents against it safely.

FAQ

Questions about start_monitoring

What does the start_monitoring tool do? +

Starts continuous MMI monitoring for a C# project. Watches .cs files and automatically analyzes on changes. Stores score history over time. It is categorised as a Execute tool in the MMI Architecture Analyzer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_monitoring? +

Register the MMI Architecture Analyzer MCP server in PolicyLayer and add a rule for start_monitoring: 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 MMI Architecture Analyzer. Nothing to install.

What risk level is start_monitoring? +

start_monitoring is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_monitoring? +

Yes. Add a rate_limit block to the start_monitoring 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 start_monitoring completely? +

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

start_monitoring is provided by the MMI Architecture Analyzer MCP server (lady-logic/mmi-analyzer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.