Low Risk

list_tutorials_by_category

Browse tutorials within a specific category, ranked by view count then publish date. Use this when a user wants to explore a topic area rather than search.

Part of the ShowMeStepByStep server.

list_tutorials_by_category 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 SHOWMESTEPBYSTEP →

Free to start. No card required.

AI agents call list_tutorials_by_category to retrieve information from ShowMeStepByStep 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_tutorials_by_category 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_tutorials_by_category": {}
  }
}

See the full ShowMeStepByStep policy for all 6 tools.

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

ENFORCE ON MY SHOWMESTEPBYSTEP →

These attack patterns abuse exactly the kind of access list_tutorials_by_category 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_tutorials_by_category only ever does what you allow.

SECURE SHOWMESTEPBYSTEP →

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

What does the list_tutorials_by_category tool do? +

Browse tutorials within a specific category, ranked by view count then publish date. Use this when a user wants to explore a topic area rather than search.. It is categorised as a Read tool in the ShowMeStepByStep MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_tutorials_by_category? +

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

What risk level is list_tutorials_by_category? +

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

Can I rate-limit list_tutorials_by_category? +

Yes. Add a rate_limit block to the list_tutorials_by_category 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_tutorials_by_category completely? +

Set action: deny in the PolicyLayer policy for list_tutorials_by_category. 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_tutorials_by_category? +

list_tutorials_by_category is provided by the ShowMeStepByStep MCP server (https://www.showmestepbystep.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ShowMeStepByStep tool call.

Deterministic rules across all 6 ShowMeStepByStep 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.