list_entity_logs

List the activity/change logs for a specific entity (e.g. an order). Requires the entity id and type.

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp

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/webcake-storefront/list-entity-logs.md

WHAT IT DOES

What list_entity_logs does on Webcake Storefront

AI agents call list_entity_logs to retrieve information from Webcake Storefront 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_entity_logs is rated Low

This tool queries and returns activity logs for entities like orders. It is a pure read operation that retrieves audit/history data without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal — an attacker with access could view audit trails, which may expose business insights or user details, but cannot alter or destroy data.

From the tool's definition 'List the activity/change logs for a specific entity' — retrieves historical data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_entity_logs safely

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

list_entity_logs Allowed

list_entity_logs 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_entity_logs": {}
  }
}

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

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

FAQ

Questions about list_entity_logs

What does the list_entity_logs tool do? +

List the activity/change logs for a specific entity (e.g. an order). Requires the entity id and type. It is categorised as a Read tool in the Webcake Storefront MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_entity_logs? +

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

What risk level is list_entity_logs? +

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

Can I rate-limit list_entity_logs? +

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

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

list_entity_logs is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Webcake Storefront, and thousands of servers like it.

This server

All 287 Webcake Storefront 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 →