get_taste_dimensions
Return all taste dimensions — user preferences inferred from kept/undone outcomes.
This record as markdown: /tools/io-github-dreamrec-livepilot/get-taste-dimensions.md
What get_taste_dimensions does on Livepilot
AI agents call get_taste_dimensions 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.
Why get_taste_dimensions is rated Low
This tool reads stored user preference information (taste dimensions) derived from past interaction history. It has no side effects, does not execute code or commands, does not modify data, and does not delete or create entries. It is a straightforward data retrieval operation, fitting the 'Read' category.
From the tool's definition The tool 'get_taste_dimensions' with description 'Return all taste dimensions — user preferences inferred from kept/undone outcomes' performs a retrieval operation. It queries and returns user preference data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs get_taste_dimensions 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 get_taste_dimensions, this is the rule to start with:
get_taste_dimensions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every get_taste_dimensions call is checked against it from then on.
Questions about get_taste_dimensions
Return all taste dimensions — user preferences inferred from kept/undone outcomes. It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.
Register the Livepilot MCP server in PolicyLayer and add a rule for get_taste_dimensions: 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.
get_taste_dimensions 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 get_taste_dimensions 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 get_taste_dimensions. 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.
get_taste_dimensions 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.
More on Livepilot, and thousands of servers like it.
This server
Across the catalogue