get_log_file_info

Get information about the project log file

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

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/caravanglory-cocos-mcp-server/get-log-file-info.md

WHAT IT DOES

What get_log_file_info does on Cocos

AI agents call get_log_file_info to retrieve information from Cocos 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_log_file_info is rated Low

This tool retrieves information about an existing log file—a read-only operation with no side effects, no code execution, and no data modification. It falls squarely into the Read category. Severity is low because log file metadata typically contains non-sensitive operational information, and misuse would only allow an agent to learn about project activity rather than cause harm.

From the tool's definition Tool name 'get_log_file_info' and description 'Get information about the project log file' indicate a retrieval operation that queries metadata about log files without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_log_file_info safely

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

get_log_file_info Allowed

get_log_file_info 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_log_file_info": {}
  }
}

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

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

FAQ

Questions about get_log_file_info

What does the get_log_file_info tool do? +

Get information about the project log file. It is categorised as a Read tool in the Cocos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_log_file_info? +

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

What risk level is get_log_file_info? +

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

Can I rate-limit get_log_file_info? +

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

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

get_log_file_info is provided by the Cocos MCP server (caravanglory/cocos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cocos, and thousands of servers like it.

This server

All 157 Cocos tools →

Across the catalogue

get_team_info on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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