Low Risk

get_parameter

Read specific TR-069 parameter values from the GenieACS cache for a device without contacting the CPE. Use this tool to quickly retrieve known parameter values such as firmware version, serial number, uptime, WiFi SSID, or IP addresses. This reads the last-known values stored in the ACS database ...

Part of the Genieacs server.

get_parameter is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE GENIEACS →

Free to start. No card required.

AI agents call get_parameter to retrieve information from Genieacs without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_parameter only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_parameter": {}
  }
}

See the full Genieacs policy for all 12 tools.

Get this rule live on your own Genieacs server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY GENIEACS →

View all 12 tools →

These attack patterns abuse exactly the kind of access get_parameter gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_parameter only ever does what you allow.

SECURE GENIEACS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_parameter tool do? +

Read specific TR-069 parameter values from the GenieACS cache for a device without contacting the CPE. Use this tool to quickly retrieve known parameter values such as firmware version, serial number, uptime, WiFi SSID, or IP addresses. This reads the last-known values stored in the ACS database — the data may be stale if the device has not informed recently. Use refresh_parameter first if you need a guaranteed fresh value from the CPE. The parameter_path can be a single parameter (e.g. "Device.DeviceInfo.SoftwareVersion") or a comma-separated list for multiple parameters. Returns the matching device document fields as JSON. Limitations: only returns data that the ACS has previously collected. If a parameter has never been read from the CPE, it will not appear in the response.. It is categorised as a Read tool in the Genieacs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_parameter? +

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

What risk level is get_parameter? +

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

Can I rate-limit get_parameter? +

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

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

get_parameter is provided by the Genieacs MCP server (genieacs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Genieacs tool call.

Deterministic rules across all 12 Genieacs tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.