Test a custom rule expression against a sample stepConfig. Evaluates a JS expression locally (no server call) to verify it returns the expected allow/block result before adding it to a role. The expression receives a
AI agents invoke test_role_access to trigger actions in Superglue MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool executes a JavaScript expression to evaluate role access rules. Even though it runs locally without a server call, it still executes arbitrary JS code supplied as input, placing it in the Execute category. The blast radius is medium since it's sandboxed to local evaluation and doesn't modify persistent state, but misuse could involve executing malicious JS logic.
From the tool's definition 'Evaluates a JS expression locally' — the tool runs arbitrary JavaScript code to test a rule expression
Documented attack patterns abuse exactly the kind of access test_role_access gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Superglue MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for test_role_access:
{
"version": "1",
"default": "deny",
"tools": {
"test_role_access": {
"limits": [
{
"counter": "test_role_access_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}test_role_access stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Test a custom rule expression against a sample stepConfig. Evaluates a JS expression locally (no server call) to verify it returns the expected allow/block result before adding it to a role. The expression receives a. It is categorised as a Execute tool in the Superglue MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Superglue MCP server in PolicyLayer and add a rule for test_role_access: 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 Superglue MCP. Nothing to install.
test_role_access is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the test_role_access 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 test_role_access. 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.
test_role_access is provided by the Superglue MCP server (superglue-ai/superglue). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Superglue MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Superglue MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.