get_logs

THE RISK

Low Risk

Why get_logs needs a policy

This tool retrieves historical log data for the current or a selected session. It is a read-only query operation that has no side effects, does not execute commands, and does not modify, delete, or move any data. The logs may contain sensitive information (e.g., search queries, product selections), but the act of retrieval itself is not destructive or dangerous.

From the tool's definition Tool name is 'get_logs' and description states it 'Returns persisted JSONL log events' — a retrieval operation with no modification or deletion of data.

Documented attack patterns abuse exactly the kind of access get_logs gives an agent:

POLICY

How to control get_logs

PolicyLayer is an MCP gateway — it sits between your AI agents and Frisco MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_logs:

policy.json

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

get_logs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Frisco MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Frisco MCP tools

Financial finish_session Opens the browser at the checkout page so you can select a delivery time and pay. Destructive clear_cart Empties the Frisco cart using the site Destructive clear_session Clears the saved session and closes the browser. Destructive remove_item_from_cart Removes a specific product from the Frisco cart by name (partial match supported). Execute login Opens a visible Chromium browser to log in to Frisco manually. Run this first to establish Write add_items_to_cart Adds products to cart by selecting from the most recent search_products result page. No ad Write update_item_quantity Changes the quantity of a product already in the cart (partial name match supported). Read check_cart_issues Checks the cart for sold-out or unavailable products and lists available substitutes for e

All 15 Frisco MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_logs

What does the get_logs tool do? +

Returns persisted JSONL log events for the current or selected session. It is categorised as a Read tool in the Frisco MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_logs? +

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

What risk level is get_logs? +

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

Can I rate-limit get_logs? +

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

Set action: deny in the PolicyLayer policy for get_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 get_logs? +

get_logs is provided by the Frisco MCP server (mkidawa/frisco-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Frisco MCP tool call.

Start from Frisco MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →