get_addon_logs

Get the last N log lines from an add-on (returns text wrapped in {logs: ...}).

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

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/fistacho-ha-nexus-agent/get-addon-logs.md

WHAT IT DOES

What get_addon_logs does on Ha Nexus Agent

AI agents call get_addon_logs to retrieve information from Ha Nexus Agent 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_addon_logs is rated Low

This tool retrieves and queries existing log data from a Home Assistant add-on. It performs no modifications, deletions, or external operations—it simply returns historical log information. The output format (text wrapped in a logs field) confirms it is a pure data retrieval operation.

From the tool's definition Tool name 'get_addon_logs' and description 'Get the last N log lines from an add-on (returns text wrapped in {logs: ...})' indicate a read-only retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_addon_logs safely

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

get_addon_logs Allowed

get_addon_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_addon_logs": {}
  }
}

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

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

FAQ

Questions about get_addon_logs

What does the get_addon_logs tool do? +

Get the last N log lines from an add-on (returns text wrapped in {logs: ...}). It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_addon_logs? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for get_addon_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 Ha Nexus Agent. Nothing to install.

What risk level is get_addon_logs? +

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

Can I rate-limit get_addon_logs? +

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

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

get_addon_logs is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ha Nexus Agent, and thousands of servers like it.

This server

All 276 Ha Nexus Agent 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 →