get_last_script_trace

Shortcut: fetch the most recent (or most recent failed) trace for a script.

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-last-script-trace.md

What get_last_script_trace does on Ha Nexus Agent

AI agents call get_last_script_trace 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.

Why get_last_script_trace is rated Low

This tool retrieves historical trace/log data from a previously-executed script. It performs a read-only query operation with no side effects on the smart home system. The data retrieved could be sensitive (logs of script execution), but the action itself is non-destructive and does not alter system state.

From the tool's definition Tool name 'get_last_script_trace' and description 'fetch the most recent (or most recent failed) trace for a script' use retrieval language ('fetch') with no indication of modification, deletion, or execution.

Questions about get_last_script_trace

What does the get_last_script_trace tool do? +

Shortcut: fetch the most recent (or most recent failed) trace for a script. 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_last_script_trace? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for get_last_script_trace: 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_last_script_trace? +

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

Can I rate-limit get_last_script_trace? +

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

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

get_last_script_trace 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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ha Nexus Agent's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.