save_analysis · Sentiment Evolution Tracker MCP

WHAT IT DOES

What save_analysis does on Sentiment Evolution Tracker

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

WHY IT NEEDS A POLICY

Why save_analysis needs a policy

This tool creates or modifies records in a persistent database by storing sentiment analysis results linked to specific customers. It is reversible (records can be updated or deleted by other means) and does not permanently destroy data or execute arbitrary code, making it a Write operation.

From the tool's definition Tool description explicitly states 'save a sentiment analysis with a customer name to the database' and 'save analysis results'. The verb 'save' combined with 'to the database' indicates data creation or modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_analysis Rate-limited

save_analysis stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_analysis": {
      "limits": [
        {
          "counter": "save_analysis_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about save_analysis

What does the save_analysis tool do? +

Explicitly save a sentiment analysis with a customer name to the database. Use this to save analysis results with a specific customer identifier. It is categorised as a Write tool in the Sentiment Evolution Tracker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_analysis? +

Register the Sentiment Evolution Tracker MCP server in PolicyLayer and add a rule for save_analysis: 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 Sentiment Evolution Tracker. Nothing to install.

What risk level is save_analysis? +

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

Can I rate-limit save_analysis? +

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

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

save_analysis is provided by the Sentiment Evolution Tracker MCP server (rubenreyesss/mcp-nlp-analytics). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.