updown_slippage_threshold

Current slippage threshold in BPS for the active round. Decays from 9500 (95%) at start to 5500 (55%) at end.

SERVERBasis MCP Server SOURCElaunch-on-basis/mcp-ts

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/launch-on-basis-mcp-ts/updown-slippage-threshold.md

WHAT IT DOES

What updown_slippage_threshold does on Basis MCP Server

AI agents call updown_slippage_threshold to retrieve information from Basis MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why updown_slippage_threshold is rated Low

The tool retrieves a current configuration value (slippage threshold in BPS) for an active round. It only reads/queries data with no side effects. Severity is low as it merely returns a numerical threshold parameter.

From the tool's definition 'Current slippage threshold' - retrieves the current slippage threshold value for the active round; describes a read-only query of a protocol parameter

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs updown_slippage_threshold safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For updown_slippage_threshold, this is the rule to start with:

updown_slippage_threshold Allowed

updown_slippage_threshold is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "updown_slippage_threshold": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every updown_slippage_threshold call is checked against it from then on.

FAQ

Questions about updown_slippage_threshold

What does the updown_slippage_threshold tool do? +

Current slippage threshold in BPS for the active round. Decays from 9500 (95%) at start to 5500 (55%) at end. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on updown_slippage_threshold? +

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

What risk level is updown_slippage_threshold? +

updown_slippage_threshold is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit updown_slippage_threshold? +

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

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

updown_slippage_threshold is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Basis MCP Server, and thousands of servers like it.

This server

All 204 Basis MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →