list_semantic_moves

A read tool on the Livepilot MCP server.

SERVERLivepilot SOURCElivepilot

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/list-semantic-moves.md

WHAT IT DOES

What list_semantic_moves does on Livepilot

AI agents call list_semantic_moves to retrieve information from Livepilot 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_semantic_moves is rated Low

The 'list' verb strongly indicates a read-only query operation that enumerates data. Even without a description, the semantic pattern aligns with retrieval. Low severity because listing data has no destructive, financial, or external execution risk. Confidence is moderate (0.75) due to the empty description—a more detailed specification would increase confidence.

From the tool's definition Tool name 'list_semantic_moves' contains the verb 'list', which typically retrieves or enumerates data without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_semantic_moves safely

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

list_semantic_moves Allowed

list_semantic_moves 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_semantic_moves": {}
  }
}

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

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

FAQ

Questions about list_semantic_moves

What does the list_semantic_moves tool do? +

list_semantic_moves is a read tool on the Livepilot MCP server. It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_semantic_moves? +

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

What risk level is list_semantic_moves? +

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

Can I rate-limit list_semantic_moves? +

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

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

list_semantic_moves is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livepilot, and thousands of servers like it.

This server

All 474 Livepilot tools →

Across the catalogue

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

Guides

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