After the successful login, the Api.GetPermissions returns a list of actions for whose execution the user is authorized.
AI agents call Api-GetPermissions to retrieve information from ThinkPLC-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing authorization metadata about the current user. It performs no modifications, deletions, executions, or financial operations. The description explicitly indicates it 'returns a list', confirming it is a read-only operation.
From the tool's definition Api-GetPermissions 'returns a list of actions for whose execution the user is authorized' — purely informational retrieval of permission metadata with no side effects.
Documented attack patterns abuse exactly the kind of access Api-GetPermissions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ThinkPLC-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for Api-GetPermissions:
{
"version": "1",
"default": "deny",
"tools": {
"Api-GetPermissions": {}
}
} Api-GetPermissions 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.
After the successful login, the Api.GetPermissions returns a list of actions for whose execution the user is authorized. It is categorised as a Read tool in the ThinkPLC-MCP MCP Server, which means it retrieves data without modifying state.
Register the ThinkPLC- MCP server in PolicyLayer and add a rule for Api-GetPermissions: 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 ThinkPLC-MCP. Nothing to install.
Api-GetPermissions 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 Api-GetPermissions 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 Api-GetPermissions. 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.
Api-GetPermissions is provided by the ThinkPLC- MCP server (mrwan84/thinkplc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ThinkPLC-MCP, 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.
23 ThinkPLC-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.