Low Risk

list_installed_microsoft_software

list_installed_microsoft_software

How to control list_installed_microsoft_software ↓

What list_installed_microsoft_software does on Allcanuse

AI agents call list_installed_microsoft_software to retrieve information from Allcanuse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_installed_microsoft_software needs a policy

This tool retrieves system state information about installed Microsoft software. It has no side effects, does not modify data, execute code, or delete resources. The blast radius of misuse is minimal—an AI agent using this tool could only gather information about what software is installed on a system, which is low-risk enumeration.

From the tool's definition Tool name 'list_installed_microsoft_software' indicates querying/enumerating installed software without modification or execution.

Documented attack patterns abuse exactly the kind of access list_installed_microsoft_software gives an agent:

How to control list_installed_microsoft_software

PolicyLayer is an MCP gateway — it sits between your AI agents and Allcanuse, and nothing reaches the server without passing your rules. This is the rule we recommend for list_installed_microsoft_software:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_installed_microsoft_software": {}
  }
}

list_installed_microsoft_software is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Allcanuse — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_installed_microsoft_software

What does the list_installed_microsoft_software tool do? +

list_installed_microsoft_software. It is categorised as a Read tool in the Allcanuse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_installed_microsoft_software? +

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

What risk level is list_installed_microsoft_software? +

list_installed_microsoft_software is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_installed_microsoft_software? +

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

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

list_installed_microsoft_software is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Allcanuse tool call.

Start from Allcanuse, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

130 Allcanuse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.