configure_downsampling · PicoScope MCP Server MCP

WHAT IT DOES

What configure_downsampling does on PicoScope MCP Server

AI agents use configure_downsampling 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 configure_downsampling needs a policy

configure_downsampling alters oscilloscope parameters to control how data is sampled. While this affects data acquisition behavior, it is a configuration change that can be reverted. It is not Destructive (data is not deleted), not Execute (it doesn't run code or arbitrary commands), and not Financial.

From the tool's definition The tool modifies oscilloscope acquisition settings (downsampling configuration) which are reversible changes to the device state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

configure_downsampling Rate-limited

configure_downsampling 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": {
    "configure_downsampling": {
      "limits": [
        {
          "counter": "configure_downsampling_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 configure_downsampling

What does the configure_downsampling tool do? +

Configure downsampling for data acquisition. 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 configure_downsampling? +

Register the PicoScope MCP Server MCP server in PolicyLayer and add a rule for configure_downsampling: 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 configure_downsampling? +

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

Can I rate-limit configure_downsampling? +

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

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

configure_downsampling 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.