Fetch and cache an OpenAPI spec from the Onboarded API. Must be called before using other operations.
AI agents call spec_sync to retrieve information from Onboarded MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation that obtains API documentation/specification. While it caches the result, caching is a benign side effect typical of read operations. There is no data modification, deletion, or code execution. The tool serves as a prerequisite for other operations but itself only fetches and stores metadata about the API, making it squarely in the Read category with low severity.
From the tool's definition Tool description states 'Fetch and cache an OpenAPI spec' — retrieves data (OpenAPI specification) from the Onboarded API without modifying or deleting anything. No side effects mentioned beyond caching, which is a read-like operation.
Attacks that exploit this kind of access
Fetch and cache an OpenAPI spec from the Onboarded API. Must be called before using other operations. It is categorised as a Read tool in the Onboarded MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Onboarded MCP Server MCP server in PolicyLayer and add a rule for spec_sync: 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 Onboarded MCP Server. Nothing to install.
spec_sync 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 spec_sync 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 spec_sync. 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.
spec_sync is provided by the Onboarded MCP Server MCP server (onboardedinc/onboarded-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 →