Query a JouleScope driver topic. Provide a relative topic such as c/fw/version or an absolute device topic.
AI agents call query_topic to retrieve information from Joulescope without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from the device without side effects. It is a read-only operation that fetches topic information from the JouleScope driver. No state changes, deletions, or external command execution are involved, making it a classic Read category tool with low severity.
From the tool's definition Tool queries a JouleScope driver topic (e.g., c/fw/version), retrieving information about device firmware, configuration, or status without modifying state.
Attacks that exploit this kind of access
Query a JouleScope driver topic. Provide a relative topic such as c/fw/version or an absolute device topic. It is categorised as a Read tool in the Joulescope MCP Server, which means it retrieves data without modifying state.
Register the Joulescope MCP server in PolicyLayer and add a rule for query_topic: 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 Joulescope. Nothing to install.
query_topic 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 query_topic 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 query_topic. 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.
query_topic is provided by the Joulescope MCP server (juanqui/joulescope-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 →