get_schema
Return field names and plain-English buyer reasons for the full registry schema or one category.
This record as markdown: /tools/dev-agentpapers-agent-papers/get-schema.md
What get_schema does on Agent Papers
AI agents call get_schema to retrieve information from Agent Papers 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 |
|---|---|---|---|
category | string | — | Optional category id. |
Parameters from the server's own tool schema.
Why get_schema is rated Low
This tool queries and returns informational schema metadata about the registry structure. It retrieves data without side effects—no data is created, modified, deleted, or executed. The action is purely informational retrieval, fitting the Read category. Severity is low because schema disclosure poses minimal immediate risk; it exposes structure rather than sensitive instance data or operational capabilities.
From the tool's definition Tool name 'get_schema' and description 'Return field names and plain-English buyer reasons' indicates retrieval of metadata/schema information only, with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs get_schema safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Papers, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_schema, this is the rule to start with:
get_schema 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 Agent Papers, apply this rule, and every get_schema call is checked against it from then on.
Questions about get_schema
Return field names and plain-English buyer reasons for the full registry schema or one category. It is categorised as a Read tool in the Agent Papers MCP Server, which means it retrieves data without modifying state.
get_schema accepts 1 parameter: category. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Papers MCP server in PolicyLayer and add a rule for get_schema: 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 Agent Papers. Nothing to install.
get_schema 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_schema 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_schema. 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_schema is provided by the Agent Papers MCP server (https://agentpapers.dev/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agent Papers, and thousands of servers like it.
This server
Across the catalogue