refresh_feature_data · Sablier MCP Server MCP: Risk & Policy

WHAT IT DOES

What refresh_feature_data does on Sablier MCP Server

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

WHY IT NEEDS A POLICY

Why refresh_feature_data needs a policy

The name implies a data refresh or update operation, which is a Write action. However, with no description available, confidence is low. It could also be a Read (fetching fresh data) or Execute (triggering a pipeline). Given sibling tools like 'add_feature' and 'add_features_batch', a Write classification is most plausible, but severity is kept medium due to uncertainty.

From the tool's definition Tool name 'refresh_feature_data' suggests updating or reloading data; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_feature_data Rate-limited

refresh_feature_data 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": {
    "refresh_feature_data": {
      "limits": [
        {
          "counter": "refresh_feature_data_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 Sablier MCP Server, so you can run agents against it safely.

FAQ

Questions about refresh_feature_data

What does the refresh_feature_data tool do? +

refresh_feature_data. It is categorised as a Write tool in the Sablier MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on refresh_feature_data? +

Register the Sablier MCP Server MCP server in PolicyLayer and add a rule for refresh_feature_data: 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 Sablier MCP Server. Nothing to install.

What risk level is refresh_feature_data? +

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

Can I rate-limit refresh_feature_data? +

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

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

refresh_feature_data is provided by the Sablier MCP Server MCP server (sablier-ai/sablier-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.