list_preference_proposals

List existing preference proposals and observations. Use this before proposing feedback so similar observations converge on one proposal.

SERVERLaguarde SOURCElaguarde-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/dev-futur-panda-laguarde/list-preference-proposals.md

WHAT IT DOES

What list_preference_proposals does on Laguarde

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

RISK

Why list_preference_proposals is rated Low

Tool queries and retrieves preference proposal records with no creation, modification, or deletion capability.

From the tool's definition List existing preference proposals and observations; retrieves historical data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_preference_proposals safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Laguarde, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_preference_proposals, this is the rule to start with:

list_preference_proposals Allowed

list_preference_proposals is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_preference_proposals": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Laguarde, apply this rule, and every list_preference_proposals call is checked against it from then on.

FAQ

Questions about list_preference_proposals

What does the list_preference_proposals tool do? +

List existing preference proposals and observations. Use this before proposing feedback so similar observations converge on one proposal. It is categorised as a Read tool in the Laguarde MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_preference_proposals? +

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

What risk level is list_preference_proposals? +

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

Can I rate-limit list_preference_proposals? +

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

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

list_preference_proposals is provided by the Laguarde MCP server (laguarde-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Laguarde, and thousands of servers like it.

This server

All 5 Laguarde tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →