get_log

THE RISK

Low Risk

Why get_log needs a policy

This tool purely queries and retrieves existing log entries from the MCP listener. It has no side effects, does not modify state, and does not execute operations. It is a simple data retrieval operation, making it a Read category tool with low severity.

From the tool's definition Tool name is 'get_log' and description states 'Get MCP listener log entries' — this retrieves log data without modifying or executing anything.

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

POLICY

How to control get_log

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

policy.json

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

get_log 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 Uefn — 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 Uefn tools

Destructive delete_actors Delete actors by their labels. Destructive delete_asset Delete an asset. Destructive tag_remove tag_remove Destructive shutdown Stop the MCP listener. Destructive snapshot_restore Restore the level to a previously saved snapshot state. Destructive undo Undo the last editor action via the transaction system. Execute batch_exec Execute multiple bridge commands in a single editor tick — faster than sending one-by-one. Execute blueprint_compile Compile a Blueprint asset and return compilation status.

All 143 Uefn 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_log

What does the get_log tool do? +

Get MCP listener log entries. It is categorised as a Read tool in the Uefn MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_log? +

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

What risk level is get_log? +

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

Can I rate-limit get_log? +

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

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

get_log is provided by the Uefn MCP server (quangdang46/uefn-verse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Uefn tool call.

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

CHECK YOUR STACK →