set_input_datetime

A write tool on the Ha Nexus Agent MCP server.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/set-input-datetime.md

WHAT IT DOES

What set_input_datetime does on Ha Nexus Agent

AI agents use set_input_datetime to create or update resources in Ha Nexus Agent, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ha Nexus Agent environment.

RISK

Why set_input_datetime is rated Medium

Likely creates or modifies datetime input entities in Home Assistant, a reversible write operation with medium impact on home automation state.

From the tool's definition uninformative description; input_datetime suggests modifying smart home temporal data

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_input_datetime 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 set_input_datetime, this is the rule to start with:

set_input_datetime Rate-limited

set_input_datetime stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_input_datetime": {
      "limits": [
        {
          "counter": "set_input_datetime_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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 set_input_datetime call is checked against it from then on.

FAQ

Questions about set_input_datetime

What does the set_input_datetime tool do? +

set_input_datetime is a write tool on the Ha Nexus Agent MCP server. It is categorised as a Write tool in the Ha Nexus Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_input_datetime? +

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

set_input_datetime is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_input_datetime? +

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

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

set_input_datetime 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 315 Ha Nexus Agent tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →