Execute a read-only SQL query against Outdoorithm's campground and gear database. The query MUST be a SELECT statement with a LIMIT clause (max 50 rows). Only the tables listed below are accessible. AVAILABLE TABLES AND COLUMNS: composite_campground_details (PREFERRED — enriched campground view) ...
Part of the Outdoorithm server.
Free to start. No card required.
AI agents call query_database to retrieve information from Outdoorithm 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 query_database 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.
{
"version": "1",
"default": "deny",
"tools": {
"query_database": {}
}
}See the full Outdoorithm policy for all 18 tools.
These attack patterns abuse exactly the kind of access query_database gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Execute a read-only SQL query against Outdoorithm's campground and gear database. The query MUST be a SELECT statement with a LIMIT clause (max 50 rows). Only the tables listed below are accessible. AVAILABLE TABLES AND COLUMNS: composite_campground_details (PREFERRED — enriched campground view) Identity: cuid, name, state, nearest_city, rec_area_name, seo_slug, latitude, longitude, elevation Quality: avg_sentiment (0-5), review_count, google_total_reviews Sentiment Trends: sentiment_trend_direction ('improving'/'declining'/'stable'), sentiment_trend_change, sentiment_trend_baseline, sentiment_trend_recent Greenbook Safety: greenbook_vibe_score (0-100), greenbook_flag_status ('ok'/'caution'/'yellow_flag'/'red_flag'), greenbook_discrimination_count, greenbook_review_count Seasonal (1-5): best_season, summer_score, fall_score, winter_score, spring_score Experience (1-5 + bool): family_friendly_score, is_family_friendly, solitude_score, is_secluded, adventure_score, is_adventure, relaxation_score, is_relaxation Activity Scores: stargazing_score, has_stargazing, kayaking_score, has_kayaking Terrain (1-5 + bool): mountain_score/is_mountain, forest_score/is_forest, lakeside_score/is_lakeside, riverside_score/is_riverside, beach_score/is_beach, desert_score/is_desert, coastal_score/is_coastal Cell Coverage: cell_coverage_avg, cell_coverage_verizon, cell_coverage_att, cell_coverage_tmobile, cell_coverage_no_signal_pct Pricing: standard_site_fee, fee_low, fee_high Amenities (bool): potable_water, water_hookups, electricity_hookups, sewer_hookups, showers, flush_toilets, vault_toilets, dump_station, camp_store, wifi, cell_phone_service, pets_allowed Camping Types (bool): tent, rv, primitive, group, cabin_lodging, glamping Activities (bool): hiking, fishing, swimming, boating, biking, wildlife_viewing, climbing, beach_activities Features (text): accessibility_features, natural_features_and_scenery, proximity_to_water_features, sites_privacy, sites_size, best_campsites Reviews (text): common_complaints, common_criticisms, positive_highlights, user_reviews_summary, hazards, pet_related_reviews Practical (text): cell_phone_service_description, weather_and_seasons, open_and_closed_season, tips_and_recommendations, hiking_description, fishing_description, swimming_description Reservations: reservable (bool), reservation_platforms (text) campground_dimension_scores cuid, dimension_key (hiking_quality/fishing_quality/family_friendliness/etc.), raw_score (1-5), state_percentile (0-1), national_percentile (0-1), activity_mention_count, mention_sentiment_avg, confidence, evidence, state, is_applicable campground_community_scores (Greenbook detail) cuid, community_vibe_score (0-100), greenbook_flag_status, total_classified_reviews, discrimination_report_count, severe_discrimination_count, high_discrimination_count, staff_discrimination_count, camper_discrimination_count, friendly_staff_count, unfriendly_staff_count, friendly_campers_count, unfriendly_campers_count, safety_concern_mentions, hostile_symbol_mentions campground_details (LEGACY — prefer composite_campground_details) cuid, name, state, avg_sentiment (0-5), review_count gear_items Product catalog with "Name", "Price", "Manufacturer", "Weight", "ProductOverview", "Keywords", "RecommendationCategory", unique_id, slug campground_gear_recommendations campground_cuid, gear_item_id, slot_type, rank, recommendation_reason, match_score EXAMPLE QUERIES: - SELECT name, state, avg_sentiment FROM composite_campground_details WHERE state = 'CA' AND avg_sentiment >= 4.0 ORDER BY avg_sentiment DESC LIMIT 10 - SELECT cuid, dimension_key, raw_score, state_percentile FROM campground_dimension_scores WHERE dimension_key = 'hiking_quality' AND raw_score >= 4.0 ORDER BY state_percentile DESC LIMIT 20 - SELECT cuid, community_vibe_score, greenbook_flag_status FROM campground_community_scores WHERE greenbook_flag_status = 'ok' AND community_vibe_score >= 70 ORDER BY community_vibe_score DESC LIMIT 20 Args: sql_query: A SELECT query with LIMIT clause (max 50 rows) explanation: Brief description of what you're looking for (for logging). It is categorised as a Read tool in the Outdoorithm MCP Server, which means it retrieves data without modifying state.
Register the Outdoorithm MCP server in PolicyLayer and add a rule for query_database: 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 Outdoorithm. Nothing to install.
query_database 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 query_database 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 query_database. 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.
query_database is provided by the Outdoorithm MCP server (https://mcp.outdoorithm.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Outdoorithm 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.