AI agents call get-library-docs to retrieve information from Seta MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves reference documentation and code examples from a local Salesforce library. It performs a read-only query operation that returns informational content without creating, modifying, deleting, or executing any code. The low severity reflects minimal blast radius—returning incorrect or sensitive documentation could mislead a developer, but the tool itself cannot execute code or modify system state.
From the tool's definition Tool name 'get-library-docs' and description explicitly state it 'Fetches' documentation, code examples, and API details. The verb 'Fetches' indicates a retrieval operation with no modification or execution of code.
Attacks that exploit this kind of access
Fetches specific, up-to-date documentation, code examples, API details, and best practices for a given local library ID (obtained from. It is categorised as a Read tool in the Seta MCP MCP Server, which means it retrieves data without modifying state.
Register the Seta MCP server in PolicyLayer and add a rule for get-library-docs: 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 Seta MCP. Nothing to install.
get-library-docs 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-library-docs 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-library-docs. 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-library-docs is provided by the Seta MCP server (techformist/seta-mcp). 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 →