openlibrary_author_works
Get works by an author from Open Library.
This record as markdown: /tools/creativelead-unclick/openlibrary-author-works.md
What openlibrary_author_works does on UnClick
AI agents call openlibrary_author_works to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
author_id | string | — |
Parameters from the server's own tool schema.
Why openlibrary_author_works is rated Low
This tool performs a read-only query operation to retrieve bibliographic information about an author's published works from Open Library. It has no side effects, cannot modify data, and poses minimal security risk. The worst-case misuse would be excessive lookups, which is a performance concern rather than a security threat.
From the tool's definition Tool description states 'Get works by an author from Open Library' — a retrieval operation with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
The rule that runs openlibrary_author_works safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openlibrary_author_works, this is the rule to start with:
openlibrary_author_works is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every openlibrary_author_works call is checked against it from then on.
Questions about openlibrary_author_works
Get works by an author from Open Library. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
openlibrary_author_works accepts 2 parameters: limit, author_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for openlibrary_author_works: 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 UnClick. Nothing to install.
openlibrary_author_works 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 openlibrary_author_works 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 openlibrary_author_works. 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.
openlibrary_author_works is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue