AI agents call get_current_config to retrieve information from Niscope without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and context strongly indicate this reads/queries configuration state from the oscilloscope without side effects. No waveform is altered, no settings are changed, and no destructive action occurs. This is a standard read operation on instrument state. Low severity because misuse only retrieves information; the blast radius is limited to information disclosure rather than equipment damage or data loss.
From the tool's definition Tool name 'get_current_config' indicates a query/retrieval operation that reads the current configuration state of an NI oscilloscope.
Attacks that exploit this kind of access
get_current_config. It is categorised as a Read tool in the Niscope MCP Server, which means it retrieves data without modifying state.
Register the Niscope MCP server in PolicyLayer and add a rule for get_current_config: 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 Niscope. Nothing to install.
get_current_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_current_config 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.
Set action: deny in the PolicyLayer policy for get_current_config. 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.
get_current_config is provided by the Niscope MCP server (ymzds/niscope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →