get_action_logs

Fetch recent invocation history for an app

SERVERDeloc SOURCEdelocdev/deloc-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/deloc-mcp/get-action-logs.md

WHAT IT DOES

What get_action_logs does on Deloc

AI agents call get_action_logs to retrieve information from Deloc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_action_logs is rated Low

This tool only retrieves historical data about past invocations without creating, modifying, deleting, or executing anything. It is a read operation with minimal blast radius—the worst case is exposure of historical metadata about application usage.

From the tool's definition The tool 'get_action_logs' fetches (retrieves) recent invocation history for an app with no modification or side effects. The verb 'fetch' and the purpose of retrieving historical logs indicates read-only access.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_action_logs safely

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

get_action_logs Allowed

get_action_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": {
    "get_action_logs": {}
  }
}

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

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

FAQ

Questions about get_action_logs

What does the get_action_logs tool do? +

Fetch recent invocation history for an app. It is categorised as a Read tool in the Deloc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_action_logs? +

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

What risk level is get_action_logs? +

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

Can I rate-limit get_action_logs? +

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

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

get_action_logs is provided by the Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Deloc, and thousands of servers like it.

This server

All 45 Deloc tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →