Search for relevant Stylus documentation, code examples, and patterns. Use this to find information about Stylus SDK, Rust smart contract development, and Arbitrum.
AI agents call get_stylus_context to retrieve information from ARBuilder without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs document/knowledge base search and retrieval operations only. It queries existing documentation and examples but does not execute code, modify data, delete resources, or create financial transactions. The lack of side effects and the informational nature of search results classify this as a Read operation with low severity risk.
From the tool's definition Tool description explicitly states 'Search for relevant Stylus documentation, code examples, and patterns' and 'find information about' — these are retrieval operations with no data modification or execution.
Documented attack patterns abuse exactly the kind of access get_stylus_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ARBuilder, and nothing reaches the server without passing your rules. This is the rule we recommend for get_stylus_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_stylus_context": {}
}
}get_stylus_context 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.
Search for relevant Stylus documentation, code examples, and patterns. Use this to find information about Stylus SDK, Rust smart contract development, and Arbitrum. It is categorised as a Read tool in the ARBuilder MCP Server, which means it retrieves data without modifying state.
Register the ARBuilder MCP server in PolicyLayer and add a rule for get_stylus_context: 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 ARBuilder. Nothing to install.
get_stylus_context 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_stylus_context 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_stylus_context. 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_stylus_context is provided by the ARBuilder MCP server (quantum3-labs/arbuilder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ARBuilder, 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.
18 ARBuilder tools catalogued and risk-classified — across an index of 43,000+ MCP servers.