Low Risk

list_publications

List STIL lab publications with optional filters. Args: year: Filter by publication year author: Filter by author name (partial match) venue: Filter by venue/journal name (partial match) keyword: Filter by keyword in title

Part of the STIL Lab Assistant server.

list_publications is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE STIL LAB ASSISTANT →

Free to start. No card required.

AI agents call list_publications to retrieve information from STIL Lab Assistant without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_publications only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_publications": {}
  }
}

See the full STIL Lab Assistant policy for all 8 tools.

Get this rule live on your own STIL Lab Assistant server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY STIL LAB ASSISTANT →

These attack patterns abuse exactly the kind of access list_publications gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so list_publications only ever does what you allow.

SECURE STIL LAB ASSISTANT →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the list_publications tool do? +

List STIL lab publications with optional filters. Args: year: Filter by publication year author: Filter by author name (partial match) venue: Filter by venue/journal name (partial match) keyword: Filter by keyword in title. It is categorised as a Read tool in the STIL Lab Assistant MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_publications? +

Register the STIL Lab Assistant MCP server in PolicyLayer and add a rule for list_publications: 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 STIL Lab Assistant. Nothing to install.

What risk level is list_publications? +

list_publications is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_publications? +

Yes. Add a rate_limit block to the list_publications 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.

How do I block list_publications completely? +

Set action: deny in the PolicyLayer policy for list_publications. 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.

What MCP server provides list_publications? +

list_publications is provided by the STIL Lab Assistant MCP server (oci:ghcr.io/khalid-tounoussi-1/stil-ets-mcp:1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every STIL Lab Assistant tool call.

Deterministic rules across all 8 STIL Lab Assistant tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.