Resolves library, framework, or technology names (like Apex, LWC, Visualforce, SOQL, DML, Triggers, Batch Apex, Asynchronous Apex, Salesforce APIs) into a unique local documentation ID. Returns detailed information about libraries including difficulties, use cases, semantic groups, and learning p...
AI agents call get-library-id 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 queries local documentation to map technology names to IDs and retrieve structured information about Salesforce libraries, frameworks, and learning resources. There is no data creation, modification, deletion, code execution, or financial impact. It is a straightforward read operation analogous to a search or lookup utility.
From the tool's definition Tool 'resolves' names 'into a unique local documentation ID' and 'Returns detailed information about libraries' — purely informational retrieval with no side effects. Description emphasizes documentation lookup and code examples.
Attacks that exploit this kind of access
Resolves library, framework, or technology names (like Apex, LWC, Visualforce, SOQL, DML, Triggers, Batch Apex, Asynchronous Apex, Salesforce APIs) into a unique local documentation ID. Returns detailed information about libraries including difficulties, use cases, semantic groups, and learning paths to help make better choices. Use this tool first when you need up-to-date documentation, code examples, or best practices for Salesforce development tasks mentioned in the prompt. 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-id: 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-id 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-id 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-id. 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-id 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 →