set_timebase · PicoScope MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_timebase does on PicoScope MCP Server

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

WHY IT NEEDS A POLICY

Why set_timebase needs a policy

Based on the tool name and server context, 'set_timebase' likely configures the time scale/sampling rate on a PicoScope oscilloscope, which is a reversible configuration change (Write). Confidence is reduced due to empty description. Severity is medium as misconfiguration could affect data acquisition quality but is reversible.

From the tool's definition Tool name 'set_timebase' and server context of oscilloscope configuration; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_timebase Rate-limited

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

FAQ

Questions about set_timebase

What does the set_timebase tool do? +

set_timebase. It is categorised as a Write tool in the PicoScope 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 set_timebase? +

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

What risk level is set_timebase? +

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

Can I rate-limit set_timebase? +

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

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

set_timebase is provided by the PicoScope MCP Server MCP server (markuskreitzer/picoscope_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.