Get the CityJS London 2026 schedule. Can filter by day (day1=Apr 15 meetup, day2=Apr 16 workshops, day3=Apr 17 main conference).
AI agents call get_schedule to retrieve information from CityJS London 2026 Companion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves conference schedule information without any side effects. It queries and returns data (schedule filtered by day) with no capability to modify, delete, or execute operations. It is purely informational read access to a public conference schedule.
From the tool's definition Tool description states 'Get the CityJS London 2026 schedule' with filtering options by day. Uses verb 'Get' which indicates data retrieval. No modification, deletion, execution, or financial operations are mentioned.
Documented attack patterns abuse exactly the kind of access get_schedule gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CityJS London 2026 Companion, and nothing reaches the server without passing your rules. This is the rule we recommend for get_schedule:
{
"version": "1",
"default": "deny",
"tools": {
"get_schedule": {}
}
}get_schedule is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the CityJS London 2026 schedule. Can filter by day (day1=Apr 15 meetup, day2=Apr 16 workshops, day3=Apr 17 main conference). It is categorised as a Read tool in the CityJS London 2026 Companion MCP Server, which means it retrieves data without modifying state.
Register the CityJS London 2026 Companion MCP server in PolicyLayer and add a rule for get_schedule: 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 CityJS London 2026 Companion. Nothing to install.
get_schedule 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_schedule 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_schedule. 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_schedule is provided by the CityJS London 2026 Companion MCP server (tejasq/basically-mcp-apps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CityJS London 2026 Companion, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 CityJS London 2026 Companion tools catalogued and risk-classified — across an index of 43,000+ MCP servers.