Low Risk

list_solutions

List Dataverse solutions (uniquename is used to filter list_entities)

How to control list_solutions ↓

What list_solutions does on Dataverse

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

Low Risk

Why list_solutions needs a policy

This tool retrieves and lists existing Dataverse solutions without creating, modifying, deleting, or executing operations. It is a read-only query with no side effects, making it a Read category risk with low severity.

From the tool's definition Tool name 'list_solutions' and description 'List Dataverse solutions' explicitly indicate a retrieval/query operation with no modification. The purpose is to enumerate solutions for filtering downstream operations.

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

How to control list_solutions

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

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

list_solutions 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 Dataverse — 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_solutions

What does the list_solutions tool do? +

List Dataverse solutions (uniquename is used to filter list_entities). It is categorised as a Read tool in the Dataverse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_solutions? +

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

What risk level is list_solutions? +

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

Can I rate-limit list_solutions? +

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

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

list_solutions is provided by the Dataverse MCP server (rededis/dataverse-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Dataverse tool call.

Start from Dataverse, 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.

22 Dataverse 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.