detect_local_powerbi_desktop
AI agents call detect_local_powerbi_desktop to retrieve information from Semantic Model MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to scan or identify local Power BI Desktop installations/instances, which is a read-only discovery operation. However, confidence is moderate (0.7) because the description is empty, making the exact behavior unclear. If it merely detects presence without side effects, it remains a Read operation with low blast radius.
From the tool's definition Tool name 'detect_local_powerbi_desktop' suggests discovery or detection of local Power BI Desktop instances.
Attacks that exploit this kind of access
detect_local_powerbi_desktop. It is categorised as a Read tool in the Semantic Model MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Semantic Model MCP Server MCP server in PolicyLayer and add a rule for detect_local_powerbi_desktop: 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 Semantic Model MCP Server. Nothing to install.
detect_local_powerbi_desktop 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 detect_local_powerbi_desktop 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 detect_local_powerbi_desktop. 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.
detect_local_powerbi_desktop is provided by the Semantic Model MCP Server MCP server (nahtheking/semantic-model-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 →