get_device_available_controls
AI agents call get_device_available_controls to retrieve information from ThinQ Connect MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and method name suggest querying what control options are available on a device, which is information retrieval with no side effects. Empty description reduces confidence slightly, but naming convention and positioning among other Read-category siblings strongly indicate this queries available controls rather than executing them.
From the tool's definition Tool name 'get_device_available_controls' with 'get' prefix indicates data retrieval. Description is empty, limiting certainty. In context with sibling tools (get_device_list, get_device_status) that are clearly Read operations, this follows the same pattern.
Documented attack patterns abuse exactly the kind of access get_device_available_controls gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ThinQ Connect MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_device_available_controls:
{
"version": "1",
"default": "deny",
"tools": {
"get_device_available_controls": {}
}
}get_device_available_controls is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_device_available_controls. It is categorised as a Read tool in the ThinQ Connect MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ThinQ Connect MCP Server MCP server in PolicyLayer and add a rule for get_device_available_controls: 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 ThinQ Connect MCP Server. Nothing to install.
get_device_available_controls is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_device_available_controls 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.
Set action: deny in the PolicyLayer policy for get_device_available_controls. 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.
get_device_available_controls is provided by the ThinQ Connect MCP Server MCP server (thinq-connect/thinqconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ThinQ Connect MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 ThinQ Connect MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.