Search for ObjectScript documentation and examples (solo en caché local)
AI agents call search_objectscript to retrieve information from IRIS ObjectScript MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches and retrieves documentation and examples from a local cache. It performs a query operation that returns information without creating, modifying, deleting, or executing code. This is a straightforward Read operation with minimal risk since it only accesses reference documentation stored locally.
From the tool's definition Tool name 'search_objectscript' and description 'Search for ObjectScript documentation and examples' indicate retrieval of documentation and examples without modification.
Attacks that exploit this kind of access
Search for ObjectScript documentation and examples (solo en caché local). It is categorised as a Read tool in the IRIS ObjectScript MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IRIS ObjectScript MCP Server MCP server in PolicyLayer and add a rule for search_objectscript: 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 IRIS ObjectScript MCP Server. Nothing to install.
search_objectscript 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 search_objectscript 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 search_objectscript. 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.
search_objectscript is provided by the IRIS ObjectScript MCP Server MCP server (sorodriguezz/iris-mcp-intelligence). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →