This record as markdown: /tools/io-github-dreamrec-livepilot/rank-by-taste-and-identity.md
What rank_by_taste_and_identity does on Livepilot
AI agents call rank_by_taste_and_identity 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 rank_by_taste_and_identity is rated Low
The tool name indicates a ranking/evaluation function, which is fundamentally a read operation that queries or scores existing data without side effects. The lack of any write, execute, or delete keywords in the name, combined with the read-focused context of sibling analysis tools, supports a Read classification.
From the tool's definition Tool name 'rank_by_taste_and_identity' suggests a ranking or evaluation operation with no parameters that would modify or delete data. No description provided.
Attacks that exploit this kind of access
The rule that runs rank_by_taste_and_identity 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 rank_by_taste_and_identity, this is the rule to start with:
rank_by_taste_and_identity 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 rank_by_taste_and_identity call is checked against it from then on.
Questions about rank_by_taste_and_identity
rank_by_taste_and_identity 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.
Register the Livepilot MCP server in PolicyLayer and add a rule for rank_by_taste_and_identity: 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.
rank_by_taste_and_identity 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 rank_by_taste_and_identity 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 rank_by_taste_and_identity. 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.
rank_by_taste_and_identity 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